Add use of pytest-retry for tests known to be flaky #3898
Merged
Conversation
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
Member
Author
|
This run demonstrates that retrying will work for the unstable x86_64 test. |
4 tasks
Member
Author
|
I've now had 6 successful passes of this workflow... that's not exactly a "fix", but it's a lot more reliable that it was. |
Member
|
Ooh! When I get home tonight (your tomorrow morning), I can try this out and hopefully confirm it fixes #3295 locally for me. |
mhsmith
approved these changes
Nov 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adds the use of pytest-retry on tests that are known to have intermittent failures.
This doesn't fix the underlying problem; but given some of these failures seem to be caused by slow machines, and some are caused by GitHub not maintaining a reliable connection to the internet, it seems a pragmatic approach.
Fixes #3295
Fixes #3897
PR Checklist: