ci: cap Build & Test at 30 minutes - #4055
Merged
Merged
Conversation
A green Build & Test run is ~5-10 min. Without a job timeout it inherits the 6h default, so a flaky test that leaks a handle (orphan node process) hangs the whole job to the 6h limit and burns a runner. 30 min is a wide margin over a normal run while failing fast on such hangs.
B4nan
added
adhoc
B4nan
enabled auto-merge (squash)
August 20, 2026 08:23
janbuchar
approved these changes
Aug 26, 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
3 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.
Summary
Build & Testhas notimeout-minutes, so it inherits GitHub's 6h default. A green run takes about 5 to 10 minutes, but a flaky test that leaks a handle (an orphan node process that never exits) hangs the whole job until the 6h kill. That burns a runner and leaves the PR red for hours.This just happened on #4052: node 22 and 26 hung to the 6h limit while node 24 passed in about 10 minutes, and a plain rerun then passed all three in about 5 minutes. Same code, same PR, so it was a flaky hang rather than a real failure.
Capping the job at 30 minutes keeps a wide margin over a normal run while failing fast on these hangs.
test-e2e.ymlalready sets a step-level timeout, so this follows existing practice.