Evaluate unit tests using multiple Clients on the same thread

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the process of doing SERVER-70032, I tried to add an assertion to CurOp that Client::getCurrent() == opCtx->getClient(), but this fails because we have unit tests that use multiple Clients on the same thread. See DBRAIITestFixture.

      We also have many unit tests that never call Client::setCurrent(), also causing this assertion to fail.

      We should evaluate whether these tests should be modified or if this is a flawed assertion.

              Assignee:
              Unassigned
              Reporter:
              Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: