ci(tests): bound the bats job with timeout-minutes: 15#210
Merged
Conversation
The required bats job (ubuntu/macos) had no timeout, so a hung runner or test could pin the REQUIRED status check for GitHub's 6h default — observed with a macOS runner stuck in_progress for 30+ min, blocking a release PR. The suite normally finishes in ~5 min; 15 fails fast and is re-runnable. bats-windows already had its own timeout.
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 a 15-minute
timeout-minutesto the requiredbatsjob (ubuntu/macos).The suite normally finishes in ~5 minutes, but a stalled macOS runner left a required check hung for ~33 minutes (the default GitHub job timeout is 6h), pinning the PR. Bounding the job makes a stall fail fast and re-runnable instead of blocking.
bats-windowsalready sets its own timeout; this covers ubuntu/macos.