Avoid using LockerNoop outside of unit tests

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2021-09-20, Execution Team 2021-10-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Benety Goh
              Reporter:
              Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: