-
Type:
Engineering Test
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-05-25
-
None
-
None
-
None
-
None
-
None
-
None
-
None
For any tests that couldn't test the write conflict failpoint due to it not being storage engine agnostic, we can enable some more unit testing to exercise write conflict handling! woooohoooo
- depends on
-
SERVER-126328 Have a storage engine-agnostic way to turn on write conflict fail points in unit tests
-
- Closed
-
-
SERVER-124273 Test for write conflicts during _next() find-fallback
-
- Open
-