fix(e2e): bound provision/mint/reap fetches at 45s (hang → fast retry)#210
Merged
Conversation
playwright.live.config sets a test timeout but NO per-request timeout, so a provision (CREATE) or reap (DROP) that intermittently HANGS on postgres-customers contention runs until the whole test dies (seen as 2-3min vector/cache timeouts). A hang isn't slowness — raising the test timeout just makes it last longer. Bound the provision POST, the mint, and both reap DELETEs at 45s so a hang fails fast and Playwright retries (passes when contention clears). Pairs with the orphan-customer-DB sweep that removes the contention source. 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 config has a test timeout but no per-request timeout on
request.fetch, so a provision (CREATE) or reap (DROP) that intermittently hangs on postgres-customers contention runs until the whole test dies (the 2-3min vector/cache timeouts). A hang isn't slowness — a longer test timeout just makes it last longer. Bound the provision POST + mint + both reap DELETEs at 45s → a hang fails fast → Playwright retries → passes when contention clears. Pairs with the orphan-DB sweep (removes the contention source).🤖 Generated with Claude Code