Repository navigation
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.
Fix Flaky Tests #4041
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
base: dev
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Fix Flaky Tests #4041
Changes from all commits
f16164dFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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 stepper fix in
dcc.Inputchanges what users see, but this entry only talks about tests. Can you add a separate Fixed line, e.g. "Fixdcc.Inputnumber stepper reverting to a previous value when clicked duringdebounce."?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 assert at 437 runs right after
HOME, but focus moves in a rAF, so under load it reads the old option and fails. With@flakygone that's a hard failure. Can you usewait_for_focus(dash_duo, "search")here? Also please swap thesleep(0.05)calls at 427/429/431 for waits on Option 0/1/2, and add a wait for "search" after theHOMEat 458 and for "Option 9" in place of thesleep(0.1)at 460. If a key lands before focus does, it goes to the wrong element, and the later wait just times out.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.
Same issue: the
sleep(0.2)calls at 86, 95 and 104 still gate keys on timing. Can you replace them withwait_for_focuson the first option and on "search" afterHOME? Also,wait_for_focusis now copied in two files. Could it go into a shared helper?Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.