-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Change streams
-
None
-
DB Integration & Observability
-
Fully Compatible
-
QI 2025-02-17
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The underlying test currently records the current time and opens a change stream at that time using {{startAtOperation´. }}startAtOperationTime{{is inclusive, so the change stream can observe an unrelated event. If the test is run in a loop inside the same fixture (e.g. during burn-in), it may observe the collection drop from the previous test run's}}afterEach()` cleanup. This will immediately invalidate the change stream when it is opened, which can cause flakiness.