CI: Increase 'JVM Tests' timeout by 30 minutes #20446
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
quarkus-bot
bot
added
the
area/infra-automation
geoand
approved these changes
Sep 29, 2021
|
✖ This workflow run has failed but no jobs reported an error. Something weird happened, please check the workflow run page carefully: it might be an issue with the workflow configuration itself. |
|
Why am I not surprised that the Windows job didn't make it in 4.5h? 😒 |
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.
Short term remedy. I did not go higher because TBH 4 hours are already well beyond bearable, IMO.
We need to work on efficiency and the number of modules (but reducing the number of modules alone won't help much if those are not adding much to the overall runtime).
See also: https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/CI.20JVM.20tests.20timeouts