Repository navigation
ci: set job timeouts for GitHub Actions - #27577
Merged
Merged
Conversation
Verify Vendored Code and Detect Unused Dependencies took up to 6.6 and 6.1 minutes with warm caches, so 10 minutes left too little room.
Contributor
Author
|
Thank you @comphead for the review |
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
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.
Which issue does this PR close?
Related to #25148. This follows apache/datafusion-comet#7679.
Rationale for this change
GitHub Actions defaults to six hours per job. Explicit job timeouts let CI report a hung job sooner and free its runner.
What changes are included in this PR?
ubuntu-slimrunner limit for the docs jobs, Verify Vendored Code, and Detect Unused Dependencies.What is the testing strategy for this PR?
Parsed all 20 workflows and verified every runner job has a timeout. Compared the parsed YAML against
mainto confirm the timeout additions are the only workflow changes. The existing CI-script tests, required-check mapping, and Prettier checks passed.Are there any user-facing changes?
CI jobs now stop when they reach their configured timeout.