Reduce pytest reruns from 10 to 4 to improve CI stability #8805
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
…ource usage While reruns are useful for mitigating flaky tests, a high rerun count significantly increases execution time for long-running integration tests (e.g. regtest / Docker-based setups). In the worst case, a single flaky test can run for nearly an hour, increasing the risk of GitHub Actions runner timeouts and unnecessary resource consumption. Reducing the reruns to 4 provides a better balance by: - Limiting excessive re-execution of long-running tests - Reducing overall CI runtime and runner usage - Surfacing persistent or systemic issues earlier, rather than masking them with repeated retries If a test consistently requires more than a few reruns to pass, it is likely indicative of a real issue rather than transient flakiness.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
While reruns are useful for mitigating flaky tests, a high rerun count significantly increases execution time for long-running integration tests (e.g. regtest / Docker-based setups). In the worst case, a single flaky test can run for nearly an hour, increasing the risk of GitHub Actions runner timeouts and unnecessary resource consumption.
Reducing the reruns to 4 provides a better balance by:
If a test consistently requires more than a few reruns to pass, it is likely indicative of a real issue rather than transient flakiness.
Changelog-None: CI enhancement only.