-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
Storage Execution
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently, LockerNoOp returns mostly "true" for functions that ask if a resource is locked. However, it returns "false" for isLocked() and isWriteLocked(), and will crash if you call isReadLocked().
We should enhance LockerNoOp to be able to control what answers it gives for these functions, in order to write more comprehensive unit tests that utilize it.
- related to
-
SERVER-35970 Use regular Locker during storage engine initialization
-
- Closed
-
-
-
- Closed
-