ci(gcb): Increase timeout for self-hosted integration test #1208
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
|
I was contemplating moving the self-hosted test to GitHub Actions just like the Sentry-Relay integration tests are. There could be a single job waiting for the docker image, and then both integration tests waiting on that one. Thoughts? |
priscilawebdev
approved these changes
Mar 9, 2022
tonyo
approved these changes
Mar 9, 2022
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 self-hosted integration test running in Google Cloud Build has started
failing recently by running into the 10 minute timeout on the docker-compose
step.
This PR increases the timeout from 10m to 15m.
#skip-changelog