Stabilize parallel snapshot refresh test - #5034
Merged
Merged
Conversation
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
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
Root cause
The regression test used independent 60-second bounds for each status wave. Under a loaded net9 full-suite run, the first bound could be exhausted even though the same test completed successfully in isolation, and the 15-second cancellation cleanup made the reported failure appear at roughly 75 seconds.
Impact
Test-only stabilization. Production behavior is unchanged, and the concurrency contract remains fully asserted.
Validation
dotnet format CodeIndex.sln --verify-no-changes --no-restoregit diff --check origin/main..HEADDocumentation and changelog
TESTING_GUIDE.mdentrieschangelog.d/unreleased/5015.fixed.mdFollow-up candidates
None.
Fixes #5015