Add timeout flag to test runner #14
Open
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
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.
Add timeout flag to test runner. Default set to zero (unlimited). This is different to the previous default (300s), however note GitHub actions has a built-in timeout. This defaults to 360 minutes per job so we may want to reduce this in the ffvvc/FFmpeg workflow file.
Maybe we could test the conformance bitstreams without a timeout, then the performance bitstreams with a timeout? The GitHub actions runners' performance seems to vary, so it may be difficult to derive a suitable figure which balances being meaningful with avoiding false negatives however.