[SERVER-66455] Undo ~OpMsgFuzzerFixture fix Created: 13/May/22  Updated: 29/Oct/23  Resolved: 16/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Billy Donahue Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-66385 Remove ThreadName's dependence on Thr... Closed
Related
is related to SERVER-58194 Fix undefined behavior in the destruc... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Service Arch 2022-05-30
Participants:

 Description   

ThreadContext is no longer required for ThreadName after SERVER-66385.
The rather indirect fix for SERVER-58194 is likely unnecessary now and the destructor code for OpMsgFuzzerFixture can return to its original condition.



 Comments   
Comment by Githook User [ 16/May/22 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-66455 Revert SERVER-58194 `ThreadContext` present as cleaning up `OpMsgFuzzerFixture`
Branch: master
https://github.com/mongodb/mongo/commit/290133720f2c7c4ed7fd438d136809ba7935d530

Comment by Billy Donahue [ 13/May/22 ]

Basically all that's needed is a revert of SERVER-58194.

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