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

enhance LockerNoOp

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Internal Code
    • Storage Execution

    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.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: