ci: Set timeout-minutes for CI jobs#1301
Merged
lapla-cogito merged 1 commit intowild-linker:mainfrom Nov 14, 2025
Merged
Conversation
davidlattimore
approved these changes
Nov 13, 2025
Contributor
|
I'm not sure exactly which test is the culprit — but testing on my machine also sometimes hangs (or takes significantly longer). Maybe we should investigate what's happening. |
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.
The exact cause remains unclear, but checks for
minimal-versionssometimes appear to hang (e.g. https://github.com/davidlattimore/wild/actions/runs/19277294367/job/55120115423). GitHub Actions' default timeout is 6 hours - while retries can eventually pass these checks, catching such issues early is clearly beneficial. Therefore, we'll settimeout-minutesfor each CI job. For now, we've configured all jobs with a 10-minute timeout, but based on actual execution times, a slightly shorter duration might be appropriate (though we've included some buffer to account for potential future CI time increases).