Repository navigation
ci: retry failing tests to absorb network flakes - #10
Merged
Merged
Conversation
Downloads of release binaries inside tests intermittently fail on the runner (connection resets, 504s, DNS). A failing test is now re-run up to --retries times (default 2, 30 s apart; timeouts are not retried), and the job summary lists tests that only passed after a retry. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
3 of 17 tasks
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.
Description
The
masterpush and nightly runs failed only on transient downloads (connection reset for actionlint/Lean, HTTP 504 for Nickel, DNS for Ren'Py). Tests now retry before failing:scripts/hello.py test --retries N(default 2), 30 s between attempts; timeouts are not retried.This PR changes
scripts/, so its CI runs the full suite.🤖 Generated with Claude Code