ci: cap the test job at 15 minutes#58
Open
ppkarwasz wants to merge 1 commit into
Open
Conversation
The test job had no timeout, so a hung or deadlocked test ran until GitHub's 6-hour default before failing. Tests normally finish in 2-4 minutes, so cap the job at 15 minutes to fail fast while leaving comfortable margin. Assisted-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Adds a job-level
timeout-minutes: 15to thetestjob in the Java CI workflow.Why
The
testjob had no timeout, so a hung or deadlocked test runs until GitHub's 6-hour default before the job fails (as seen on #57, where a test got into a deadlock). Tests normally finish in 2-4 minutes, so 15 minutes fails fast on a hang while leaving comfortable margin for the slowest matrix cells.The cap is job-level, so it applies to every OS/JDK matrix combination. When it fires, the
if: always()"Upload test reports" step still runs, preserving whatever surefire output exists to help locate the hang.