CI: Tighten timeout period for all jobs #101712
Merged
Conversation
This file contains 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
|
Looks good, but might be cutting it close with 10 minutes on some of these tests, static tests can run longer if downloads go slow, and unit tests can get stuck for a bit |
|
Bumped up static-checks to 30 minutes & removed the test-specific 10 minute timers |
akien-mga
approved these changes
Jan 17, 2025
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.
Fixes an issue brought up in RC chat1 where portions of a job stuck in an indefinite loop will only be timed out at the default interval of 6-hours. Now the maximum timeout period for jobs is 2 hours, with the majority being smaller than that:
Footnotes
https://chat.godotengine.org/channel/buildsystem?msg=RJiJn3G8KxA4tqbp6 ↩