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

Avoid using LockerNoop outside of unit tests

XMLWordPrintableJSON

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

      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@mongodb.com Benety Goh
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: