ci: add timeout-minutes to every matrix job so a hung job can't block merges for 6h#128
Merged
Conversation
… merges for 6h The CI matrix jobs had no `timeout-minutes`, so they inherit GitHub's 360-minute (6h) default. When a Windows `cargo test` ran slow/stuck, it left every open PR un-mergeable with no fail-fast signal — you couldn't tell a hung job from a slow one, and nothing would end it short of the 6h cap. Adds a generous per-job ceiling, set well above each job's observed duration so a legitimately-slow run never false-fails, while a genuinely-hung one fails fast enough to rerun: - rust: 90 (observed worst ~45min on Windows) - wasm: 45 - node / pack-install: 30 - bench: 20 Config-only; no gate is weakened (a timeout only bounds runtime). YAML validated (all 6 jobs parse). Co-Authored-By: claude-flow <ruv@ruv.net>
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
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.
What / why
The CI matrix jobs (
rust,wasm,node,pack-install,bench) had notimeout-minutes, so they inherit GitHub's 360-minute (6h) default. When a Windowscargo testran slow/stuck recently, it left every open PR un-mergeable with no fail-fast signal — you couldn't distinguish a hung job from a slow one, and nothing would end it short of the 6h cap.Change (config-only)
A generous per-job ceiling, set well above each job's observed duration so a legitimately-slow run never false-fails, while a genuinely-hung one fails fast enough to rerun:
No gate is weakened — a timeout only bounds runtime, caps the worst case at 90min instead of 360, and makes a true hang a visible, rerunnable failure. YAML validated (all 6 jobs parse).
🤖 Generated with claude-flow