Ci raise provisioning timeout - #6858
Merged
Merged
Conversation
180s was too tight for CI's node auto-provisioned pipeline pods, which have no warm pool by design and can take several minutes to get a fresh node under merge-queue load. Caused real merge failures (#6650).
Traced the actual worst-case timing live: node cold start plus a CSI topology-cache race on brand-new nodes together took ~9 minutes. 600s left almost no margin over that; 900s does.
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
2 participants
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.
aggtst_base.py set provisioning_timeout_secs=180 for pipeline creation, too tight for how CI actually provisions capacity. This PR raises it to 900s.