@W-23895509: Add job-level timeout to CI workflows - #127
Merged
shauryemahajanSF merged 2 commits intoAug 18, 2026
Merged
Conversation
Backstop against a wedged ubuntu-latest runner hanging up to the 6h default (as happened on an apt-get step in PR #123). Job-level cap covers all steps, current and future, with no per-step maintenance. Co-Authored-By: Claude Opus 4.8 (1M context) <claude.noreply@salesforce.com>
shauryemahajanSF
marked this pull request as ready for review
August 18, 2026 18:58
jbisaSF
approved these changes
Aug 18, 2026
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
2 participants
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
Adds
timeout-minutes: 10to the three CI jobs:test-scripts(test-scripts.yml)security(security.yml)verify-zips(verify-zip.yml)Why
On PR #123, a
test-scriptsrun hung ~38 minutes on theapt-get"Install XML tools" step because the ubuntu-latest runner was wedged — the identical step in thesecurityjob on the same commit finished in 90s, confirming it was a bad runner, not the code. Without a cap, a wedged runner runs up to GitHub's 6h default before failing.A job-level timeout is the minimal backstop: it caps the whole job (all steps, current and future) so a hung runner fails fast and is retriable, with no per-step maintenance. 10 min is generous over the normal ~2 min runtime, so it only fires on a genuine hang.
🤖 Generated with Claude Code