HDDS-8444. Increase timeout of CI build #4586
Merged
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.
What changes were proposed in this pull request?
build check in CI is frequently timing out in forks due to Maven cache miss (but not in
apache/ozone). Dependent checks (e.g. acceptance, kubernetes) can only be run after re-try. To avoid wasting time, I propose increasing time limit for build check from 30 to 45 minutes.https://issues.apache.org/jira/browse/HDDS-8444
How was this patch tested?
CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/4734224440/jobs/8402851285
build check succeeded in 36m 6s, i.e. would have failed without this change.