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

flake: deadline of `now` fails intermittently

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • Hide

      build/static_gcc_ninja/mongo/db/db_unittests --suite=DBRAIITestFixture --filter=AutoGetCollectionForReadGlobalLockDeadline

      Show
      build/static_gcc_ninja/mongo/db/db_unittests --suite=DBRAIITestFixture --filter=AutoGetCollectionForReadGlobalLockDeadline
    • Dev Tools 2020-02-10
    • 0

      Test is acquiring GlobalLock with deadline of `now()`.

      This is wrong but will succeed if the acquisition is fast and lucky enough that it can all be done in the same wallclock millisecond. In Debug builds, it fails more often because debug-only lock diagnostics make the acquisition slower, so it crosses a millisecond boundary more often and fails.

      flaky red herring found while debugging SERVER-45677

            Assignee:
            billy.donahue@mongodb.com Billy Donahue
            Reporter:
            billy.donahue@mongodb.com Billy Donahue
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: