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

Avoid using LockerNoop outside of unit tests

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0-rc0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Execution Team 2021-09-20, Execution Team 2021-10-04

      Description

      A good portion of our mock interfaces are used to make unit testing easier. The LockerNoop::isW() method was changed to always return true, as an example. However, the LockerNoop is used outside of unit tests. Returning true that the global exclusive lock is held by multiple operations can result in bugs as seen inĀ SERVER-59591.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              gregory.wlodarek Gregory Wlodarek
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: