ci: cap every job with a timeout#323
Merged
Merged
Conversation
A job with no timeout runs to GitHub's 6-hour default when it hangs, billing 360 Actions minutes from one stuck step. Sized off measured runtimes.
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.
Adds the one CI guard this repo was still missing.
What it delivers
timeout-minuteson every job that lacked one, sized off measured runtimes with generous headroom: 15 by default, 20 for in-gate image builds, 30 for multi-arch image publishes. The slowest job measured across recent runs is an 8.6-minute multi-arch build.Nothing else changes. The PR gate already declares
concurrencywithcancel-in-progressandenable-cacheon itssetup-uvsteps, and those are left exactly as they are. Release and publish workflows get a timeout only — they are never givencancel-in-progress: true, because a publish must not be cancelled mid-upload.Benefit
A job with no timeout runs to GitHub's 6-hour default when it hangs, billing 360 Actions minutes from a single stuck step. Every job now has a bounded worst case, so one hung run can no longer drain a month's allowance.