ci: retry the coverage badge push - #418
Merged
Merged
Conversation
Non-PR CI runs are grouped per commit, so back-to-back merges run the coverage-badge job concurrently. Its force push to the badges branch failed once transiently during such a burst (run 34958472308) and turned main red. Retry the push up to four times with backoff before failing.
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Summary
Since #395, non-PR CI runs are grouped per commit, so when PRs are merged back to back, the
coverage-badgejob runs for several commits at once. Its force push to thebadgesbranch failed once, transiently, during such a burst (run 34958472308, commit b69b22c), and that turned main red. Every run since has passed.The push step now retries up to 4 times, waiting 10 s, 20 s and 30 s between attempts. If all attempts fail, it prints a warning annotation and still exits non-zero, so real failures stay visible. Nothing else changes: the job still pushes a single
coverage.jsontobadgeswith--force.Verification
ci.ymlparses as YAML, and the edited step passesbash -n.pytest tests/test_phase5_backcompat.py tests/test_testpypi_workflow.py: 20 passed.