-
Type:
Build Failure
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: Flaky Test
Use Case
As a driver engineer
I want to skip flaky CSOT tests
So that development isn't intermittently impeded
User Experience
- Flaky CSOT tests should be skipped since the value of the coverage is low and the frequency of flakes is high, impeding development
Dependencies
- N/A
Risks/Unknowns
- These tests are considered low-value because it's an experimental API. We should not be impeding development to promote fixing tests that are dependant on an unstable feature.
Acceptance Criteria
Implementation Requirements
- the test suite called out in the original flake ticket should be skipped
Testing Requirements
- None
Documentation Requirements
- None
Follow Up Requirements
- None
1) CSOT spec tests
legacy timeouts behave correctly for retryable operations
operation succeeds after one socket timeout - deleteOne on collection: at failOnMismatchedCount (test/tools/unified-spec-runner/match.ts:445:10)
at matchesEvents (test/tools/unified-spec-runner/match.ts:683:7)
at runUnifiedTest (test/tools/unified-spec-runner/runner.ts:250:22)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Context.<anonymous> (test/tools/unified-spec-runner/runner.ts:336:13)
- is duplicated by
-
NODE-6859 Flaky: CSOT spec test: operation succeeds after one socket timeout - listDatabases on client [1]
-
- Closed
-
-
NODE-6863 Flaky: operation succeeds after one socket timeout - aggregate on collection [1]
-
- Closed
-
-
NODE-6867 Flaky: operation fails after two consecutive socket timeouts - <operation> on collection [8]
-
- Closed
-