-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: flaky tests Queued Confirmations...
in FF for unordered events
#30031
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
@@ -312,7 +312,7 @@ describe('Queued Confirmations', function () { | |||
// create deposit transaction in dapp 1 | |||
await createDepositTransaction(driver); | |||
|
|||
await driver.delay(2000); | |||
await driver.delay(5000); | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the buffer time needs to be a bit bigger otherwise the metric events get unordered, and we get first the signature event from the dapp2 (localhost:8081) and the asserts fail
@@ -420,7 +420,7 @@ async function switchChainToDappOne(driver: Driver) { | |||
// No dialog should appear as we already gave permissions to this network | |||
await driver.waitForSelector({ | |||
css: '[id="chainId"]', | |||
text: '0x539', | |||
text: '0x3e8', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my mistake, we should wait for the new chain id (changed 2 steps above)
Builds ready [ba5f69e]
Page Load Metrics (1567 ± 83 ms)
Bundle size diffs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM ! |
Queued Confirmations...
in FF for unordered events
Description
An unordered metric event makes the test fail, as we see the signature one (performed after in 8081) instead of the tx one (performed first in 8080)
After looking at the logs, we can see how the 8081 event refers to the signature event that happens after the transaction
Furthermore, the wait for chainID added here was pointing to the old chainId, so now it's corrected and fixes remaining flakiness
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist