-
Notifications
You must be signed in to change notification settings - Fork 42
Fix 2 flaky Cypress e2e specs on fix_e2e_tests_failing #3390
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
Merged
+17
−11
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
65c4185
Fix 2 flaky Cypress e2e specs on fix_e2e_tests_failing
vivi-the-going-merry[bot] 602cfce
Fix root cause of 2 flaky Cypress e2e specs, not just symptoms
vivi-the-going-merry[bot] ca23efe
Fix identical race on .published > .current assertion
vivi-the-going-merry[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Non-blocking — PR description is stale against this code. The PR body's "What changed" says: "Gave the one racing assertion in each spec
{ timeout: 10000 }rather than reaching for{ force: true }" and diagnoses the root cause as a mount-race/0-height timing issue. That described the first commit's fix here (65c4185: a{ timeout: 10000 }bump on the first selector). This second commit (602cfce, "Fix root cause... not just symptoms") replaced that withscrollIntoView()and this comment explicitly says the opposite — "not a render-timing race (a longer timeout never resolves it)". The description was never updated to match, so it now misdescribes the actual root cause and fix for this file (it's still accurate forsearchFunctionality.cy.js). Worth a quick edit so anyone debugging a future flake here isn't pointed at the wrong theory.