[SERVER-31247] enhance LockerNoOp Created: 25/Sep/17  Updated: 06/Dec/22  Resolved: 24/Jun/19

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-35970 Use regular Locker during storage eng... Closed
related to SERVER-26879 Get rid of LockerNoop Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

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.



 Comments   
Comment by Sara Williamson [ 24/Jun/19 ]

Instead, we plan to do SERVER-26879.

Generated at Thu Feb 08 04:26:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.