Fix flaky connection pool tests for FIFO ordering #3751
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 is a test. Using copilot and the github mcp to fix a github issue
Description
This PR fixes two flaky unit tests in
ChannelDbConnectionPoolTestthat were failing intermittently due to race conditions in their synchronization logic.Changes
GetConnectionMaxPoolSize_ShouldRespectOrderOfRequest(sync version)ManualResetEventSlim+CountdownEventsynchronization with more robust coordination using multipleManualResetEventSliminstancesSpinWaitto ensure tasks are properly ready before starting requests[ActiveIssue]attribute - test is now stableGetConnectionAsyncMaxPoolSize_ShouldRespectOrderOfRequest(async version)[ActiveIssue]attribute - test is now stableRoot Cause
The original tests had race conditions where:
Validation
✅ Both tests now pass consistently across all target frameworks:
Total: 30/30 test executions passed (100% success rate)
The tests now reliably validate that
ChannelDbConnectionPoolcorrectly respects FIFO ordering when the pool reaches maximum capacity and connections need to be queued.Fixes
Fixes #3730