fix(ci): extend 'go test' timeout to 20 min #599
Merged
Conversation
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
brookesargent
approved these changes
Jan 13, 2025
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.
We've had some CI runs fail with timeouts against the EU region: likely the increased latency just having things take that much longer.
A previous attempt to extend the timeout of the integration test step in the GHA Workflow forgot that the default timeout for
go testis 10 minutes 🙃. This extends that to 20 for the provider's integration tests and adjusts the GHAtimeout-minutesvalues (as the default is 360 minutes)Fly by fix for the "Validate Examples" job which started failing due to the update to
ubuntu-latestfrom what I can tell (which no longer hasterraforminstalled by default)