-
Type: Bug
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: CMAP
-
None
-
Needed - No Spec Changes
-
Summary
pool-checkout-maxConnecting-is-enforced test occasionally fails for .net. The test assumes certain timing of events, which does not hold in ~0.5%-1% of executions.
Motivation
Who is the affected end user?
Drivers
How does this affect the end user?
Flaky test
How likely is it that this problem or use case will occur?
Main path? Edge case?
If the problem does occur, what are the consequences and how severe are they?
Flaky test
Is this issue urgent?
No
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
Yes
Acceptance Criteria
What specific requirements must be met to consider the design phase complete?
- is related to
-
CSHARP-3995 Fix flaky pool-checkout-maxConnecting-is-enforced.json:maxConnecting_is_enforced
- Closed
- split to
-
CDRIVER-5531 Racy pool-checkout-maxConnecting-is-enforced test
- Backlog
-
CXX-3005 Racy pool-checkout-maxConnecting-is-enforced test
- Backlog
-
GODRIVER-3179 Racy pool-checkout-maxConnecting-is-enforced test
- Backlog
-
RUBY-3443 Racy pool-checkout-maxConnecting-is-enforced test
- Backlog
-
RUST-1911 Racy pool-checkout-maxConnecting-is-enforced test
- Backlog
-
CSHARP-5037 Racy pool-checkout-maxConnecting-is-enforced test
- Closed
-
NODE-6077 Racy pool-checkout-maxConnecting-is-enforced test
- Closed
-
PHPLIB-1431 Racy pool-checkout-maxConnecting-is-enforced test
- Closed
-
MOTOR-1297 Racy pool-checkout-maxConnecting-is-enforced test
- Closed
-
PYTHON-4362 Racy pool-checkout-maxConnecting-is-enforced test
- Closed
-
JAVA-5417 Racy pool-checkout-maxConnecting-is-enforced test
- Closed