ci/gha: add job timeouts #3984
Merged
ci/gha: add job timeouts #3984
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
The default timeout is 360 minutes, which is way long for these jobs. If the CI (or a test) has stuck, we'd better know about it earlier than in 6 hours. Set the timeouts for some [relatively] long running jobs conservatively: - test and release jobs usually take ~10 minutes; - lint job takes 1 minute (but can be a few times slower when we switch Go or golangci-lint version); - cross-386 job takes about 2 minutes; - the rest is seconds (and I am lazy to set timeouts everywhere). Signed-off-by: Kir Kolyshkin <[email protected]>
kolyshkin
force-pushed
the
gha-timeouts
branch
from
4f3aadb
to
b22073c
Compare
AkihiroSuda
approved these changes
Aug 17, 2023
If there is a configuration item in |
lifubang
approved these changes
Aug 17, 2023
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.
The default timeout is 360 minutes, which is way long for these jobs. If the CI (or a test) has stuck, we'd better know about it earlier than in 6 hours.
Set the timeouts for some [relatively] long running jobs conservatively:
Inspired by #3953/#3982.