[SERVER-73185] Evaluate unit tests using multiple Clients on the same thread Created: 23/Jan/23  Updated: 24/Jan/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-70032 Collect and report operation CPU time... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

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.


Generated at Thu Feb 08 06:23:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.