test: resolve flaky timeout in issue-3356#5188
Merged
Merged
Conversation
Assisted-by: claude:opus-4.6 Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5188 +/- ##
==========================================
- Coverage 93.28% 93.26% -0.02%
==========================================
Files 110 110
Lines 36313 36313
==========================================
- Hits 33873 33869 -4
- Misses 2440 2444 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
3 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.
This relates to...
Fixes: #5179
Rationale
The
issue-3356.jstest is flaky, intermittently timing out after 180s. The root cause is a mismatch between thebodyTimeout: 50(50ms) and undici's fast timer resolution (~1s). The timeout soemtimes doesn't fire before the server completes its 100ms delayed response, leaving the assertion plan unsatisfied and the test hanging.Changes
Features
N/A
Bug Fixes
bodyTimeoutto 1500ms (above the ~1s timer resolution)fastTimersTick(2000)to deterministically advance the clock past the timeout thresholdminTimeout/maxTimeoutto RetryAgent to reduce unnecessary retry delay in the testBreaking Changes and Deprecations
N/A
Status
Assisted-by: claude:opus-4.6