ci: cap CI job runtime at 15 minutes#233
Merged
Merged
Conversation
Add timeout-minutes to the CI matrix job so a hung runner is killed at 15 minutes instead of GitHub's default 360-minute cap. macOS hangs billed at the 10x multiplier were the main quota drain; builds finish in ~1-3 minutes, leaving wide margin.
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
timeout-minutes: 15to the CI matrix job so a hung runner is cancelled at 15 minutes instead of inheriting GitHub's default 360-minute cap.CI run
27243212776had its macOS leg hang for the full 360 minutes (23:46 June 9 → 05:47 June 10) before cancellation, while linux and windows finished in ~1-2 min. macOS minutes bill at a 10x multiplier, so that single hang cost ~3,450 billed minutes. A scan of the last ~60 runs shows macOS normally completes in ~1 min, so 15 minutes leaves wide margin while capping the worst case.The timeout is set at the job level, so it protects all three matrix legs (linux, windows, macOS).
Closes #232