fix(e2e): raise live provision/claim-deploy timeout 120→180s (de-flake)#209
Merged
Conversation
…s (de-flake) The live-provision (vector/cache/nosql/db) + claim-deploy legs do real prod provisioning + an assert-usable connect from the CI runner. Normally ~14s, but under prod contention they intermittently spike past the 120s default and time out — and since both files are serial groups, one slow flow aborts the rest (seen as vector/cache 2min timeouts that pass on retry). Raise the per-test budget to 180s so transient prod latency stops redding the suite; the test still verifies the flow WORKS, and retries cover the rest. Pairs with the cadence right-size (#208/#277) that removes the self-inflicted load. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
size-limit report 📦
|
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.
The live-provision (vector/cache/nosql/db) + claim-deploy legs do real prod provisioning + an assert-usable connect from the CI runner — normally ~14s, but under prod contention they intermittently spike past the 120s default and time out; since both files are serial groups, one slow flow aborts the rest (the vector/cache 2-min timeouts that pass on retry). Raise the per-test budget to 180s so transient prod latency stops redding the suite. Pairs with the cadence right-size (#208/#277) that removes the self-inflicted load, and the DB-leak cleanup that reduces
CREATE DATABASEcontention.🤖 Generated with Claude Code