Repository navigation
Increase AzureCI timeout to 120 minutes instead of using the default of 60 minutes - #4854
Merged
Merged
Conversation
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
bsideup
approved these changes
Jan 5, 2022
Member
Author
|
Lovely, flaky Cosmos test failing, thank you very much and what a coincidence 🙇 |
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
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.
After evicting the Gradle Remote Cache, we saw our Windows10 build on AzureCI timeout:
https://dev.azure.com/testcontainers/testcontainers-java/_build/results?buildId=11729&view=logs&j=28ca4d66-d8a1-504b-08ee-20bf28cc3e75
However, it is reasonable that a completely uncached build of the whole project takes more than 60 minutes, so this PR increases the timeout to 120 minutes.
An alternative would be to use no timeout (which is possible on self-hosted notes), but this would carry the risk of blocking our Windows CI in case of hanging builds.