ci: raise 'run tests' step timeout to 20 minutes - #4120
Merged
Conversation
The stable-check (windows-latest) job on main timed out at the 10-minute step limit while all 7466 tests were passing on every target — the suite has simply outgrown the limit on the slower Windows runners (run 32375552764). Bump the timeout for the shared ./.github/actions/test step to 20 minutes in all three workflows that use it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR increases the GitHub Actions step timeout for the shared “run tests” composite action to accommodate longer runtimes on windows-latest, reducing spurious CI failures due to the previous 10-minute cap.
Changes:
- Increased the
run testssteptimeout-minutesfrom 10 to 20 instable-check. - Increased the
run testssteptimeout-minutesfrom 10 to 20 inbleeding-check. - Increased the
run testssteptimeout-minutesfrom 10 to 20 inpre-release-check.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/stable-check.yml | Bumps the run tests step timeout to 20 minutes. |
| .github/workflows/bleeding-check.yml | Bumps the run tests step timeout to 20 minutes. |
| .github/workflows/pre-release-check.yml | Bumps the run tests step timeout to 20 minutes. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Collaborator
Coverage Report for CI Build 6244Coverage remained the same at 90.747%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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.
Problem
stable-check (windows-latest)onmainfailed in run 32375552764: the run tests step hit its 10-minutetimeout-minuteslimit. The log shows all 7466 tests passing on each target right up to##[error]The action has timed out.— the suite has simply outgrown the limit on the slower Windows runners.Change
Bump
timeout-minutesfrom 10 to 20 for the shared./.github/actions/teststep in all three workflows that use it (stable-check,bleeding-check,pre-release-check), since they run the identical suite on the samewindows-latestrunners.Low risk: this only widens the flake ceiling; a genuinely hung run still gets killed, just 10 minutes later.
🤖 Generated with Claude Code