Fix race in CompatibleFirstStress lock manager test

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Trivial - P5
    • 3.4.11, 3.6.2, 3.7.1
    • Affects Version/s: 3.7.1
    • Component/s: Storage
    • None
    • Fully Compatible
    • v3.6, v3.4
    • Storage 2017-12-18
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      A call to lockComplete with timeout 0 may return LOCK_WAITING even though another thread already was notified. So the invariant that lockComplete must succeed if another thread is holding a MODE_S lock is invalid.

      
      

            Assignee:
            Geert Bosch
            Reporter:
            Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: