Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase AzureCI timeout to 120 minutes instead of using the default of 60 minutes #4854

Merged
merged 1 commit into from
Jan 5, 2022

Conversation

kiview
Copy link
Member

@kiview kiview commented Jan 5, 2022

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.

@kiview
Copy link
Member Author

kiview commented Jan 5, 2022

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kiview kiview added this to the next milestone Jan 5, 2022
@kiview
Copy link
Member Author

kiview commented Jan 5, 2022

Lovely, flaky Cosmos test failing, thank you very much and what a coincidence 🙇
But only on GHA, Windows build succeeded, also thanks to more cache now.

@kiview kiview merged commit e70782a into master Jan 5, 2022
@delete-merged-branch delete-merged-branch bot deleted the increase-azure-timeout branch January 5, 2022 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants