Rerun e2e tests in CI due to flakyness #503
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
Signed-off-by: Samuel Monson <[email protected]>
markurtz
approved these changes
Dec 9, 2025
jaredoconnell
approved these changes
Dec 10, 2025
Collaborator
jaredoconnell
left a comment
jaredoconnell
left a comment
There was a problem hiding this comment.
Seems like an improvement, but it seems like it's working around a larger issue. Have we identified the typical causes of failure?
Collaborator
Author
Flakiness in end-to-end is due to timeouts since GitHub runners have shared compute. |
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.
Summary
The e2e tests fail all of the time in CI due to unpredicable compute time. This PR uses
pytest-rerunfailuresto rerun failing tests up to 3 times.Use of AI
## WRITTEN BY AI ##)