Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31247

enhance LockerNoOp

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal Code
    • Storage Execution

      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.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: