CI - Set Unity testsuite timeout to 30m#3015
Merged
Merged
Conversation
jdetter
approved these changes
Aug 1, 2025
mamcx
pushed a commit
that referenced
this pull request
Aug 26, 2025
# Description of Changes Just what it says on the can. This test suite can sometimes mysteriously hang for a long time, so a timeout will help kill this (and free up resources) earlier. # API and ABI breaking changes None # Expected complexity level and risk 1 # Testing None really. I guess I could test this by adding a step that just sleeps forever, but this is basically just setting some data. Co-authored-by: Zeke Foppa <bfops@users.noreply.github.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
2 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.
Description of Changes
Just what it says on the can. This test suite can sometimes mysteriously hang for a long time, so a timeout will help kill this (and free up resources) earlier.
API and ABI breaking changes
None
Expected complexity level and risk
1
Testing
None really. I guess I could test this by adding a step that just sleeps forever, but this is basically just setting some data.