fix(test): give stalled Antigravity body failover a 500ms budget - #402
Merged
Conversation
The 50ms timeout was too tight on loaded CI: first-body stall and the follow-up request shared a wall-clock window that production resets per endpoint. Widen only this test; keep the hung 503 body.
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
1 participant
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.
Summary
Only the stalled non-2xx Antigravity body failover test.
timeoutMs50 → 5002 * 500 + 500(1500ms)writepartial, noend)requests === 2anddone.reason === "stop"Production
streamAntigravityis unchanged. This does not claim local reproduction of CI Node 26 / Windowsrequests 1 !== 2.Test plan
bun run check; focused case ×8 8/0;antigravity.test.ts×3 37/37bun run test: this case passed (~508ms); the local suite later hung onworkflows/execute.e2e.test.tsand was killed. Vitest was not reached viarun-tests.mjs.tests/extensions/file-search/index.spec.ts30/30Node 26 is not in the current CI matrix and is not claimed here.