-
Type:
Build Failure
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
When the async interval was fixed in NODE-4638, the change stream consecutive resume spec test started failing. There appears to be a race condition - after initializing the change stream and inserting multiple documents, when the CS is iterated, no events are received. Adding a write concern of 'w': 'majority' to the inserts or adding a short sleep after the inserts is enough to allow the test to consistently pass.
Acceptance Criteria
- Determine the root cause of the failing test and fix the test
- Unskip the two skipped consecutive resume change stream tests
- Remove the manually added prose test
- duplicates
-
-
- Closed
-
- is related to
-
DRIVERS-2477 change stream consecutive resume test should use write concern majority
-
- Closed
-
- related to
-
NODE-4638 Prevent async interval from calling `fn` if `fn` is already executing
-
- Closed
-