ci: add back CI-level automatic retrying for failing int and e2e tests #9652
Conversation
This file contains 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
…2e tests, to automatically retry flaky test runs
AlessioGr
changed the title
|
🚀 This is included in version v3.3.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We should fix all the flaky tests in the future - in the meantime this PR will reduce collectively wasted engineer hours, as we now don't have to manually open the awkward GH actions UI and press the retry button - often multiple times for each PR.
It may not be enough to simply retry the test:int / test:e2e commands to get the tests not to flake for the next run, but let's see how this goes