Repository navigation
Cap every CI job, so a hung one fails in minutes rather than hours - #5
Merged
Merged
Conversation
With no timeout-minutes a job inherits the 6-hour default. lexi hit exactly that today — a Playwright leg that normally takes four minutes sat for thirty with nothing to stop it, and a job that hangs long enough stops reading as a failure at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
No workflow in this repo set
timeout-minutes, so every job inherited the 6-hour default.lexidemonstrated the cost today: its node-self-host Playwright leg hung at thirty minutes on a step that normally takes four, and nothing was going to stop it. 20 minutes is comfortably above every job here.🤖 Generated with Claude Code