Skip to content

ci: retry failing tests to absorb network flakes - #10

Merged
matbrgz merged 1 commit into
masterfrom
fix/test-retries
Oct 12, 2026
Merged

matbrgz merged 1 commit into
masterfrom
fix/test-retries

Conversation

@matbrgz

@matbrgz matbrgz commented Oct 12, 2026

Copy link
Copy Markdown
Collaborator

Description

The master push 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.
  • The job summary lists tests that passed only after a retry (🔁), so persistent flakiness stays visible.

This PR changes scripts/, so its CI runs the full suite.

🤖 Generated with Claude Code

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>
@matbrgz
matbrgz merged commit b012f77 into master Oct 12, 2026
11 checks passed
@matbrgz
matbrgz deleted the fix/test-retries branch October 12, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant