CI: Increase GKE/EKS ginkgo timeout to 3 hours #10809
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
We've been seeing more timeouts on GKE when our CI is under load and jobs wait in the queue for a free executor. The ginkgo timeout is intended to be shorter than the jenkins timeout so that cleanups can happen and so ginkgo can correctly log the timeout (instead of just being terminated). Signed-off-by: Ray Bejjani <ray@isovalent.com>
raybejjani
added
pending-review
area/CI
|
Please set the appropriate release note label. |
2 similar comments
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
|
test-gke (istio flake :( https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/216/ ) |
|
test-gke |
nebril
approved these changes
Apr 2, 2020
|
Let's merge it |
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.
amusingly, as I make this, we are at the max 5 GKE jobs allowed. This doesn't fix that, and it may fail with "cannot select cluster" instead
We've been seeing more timeouts on GKE when our CI is under load and
jobs wait in the queue for a free executor. The ginkgo timeout is
intended to be shorter than the jenkins timeout so that cleanups can
happen and so ginkgo can correctly log the timeout (instead of just
being terminated).