[SERVER-19115] Clean up how we launch async operations in catalog manager unit tests to prevent deadlocks on assertion failures Created: 24/Jun/15  Updated: 25/Jan/17  Resolved: 25/Jun/15

Status: Closed
Project: Core Server
Component/s: Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.1.5

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-19228 catalog_manager_replica_set_log_chang... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 5 06/26/16
Participants:

 Comments   
Comment by Githook User [ 25/Jun/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-19115 Move async helper code to NetworkTestEnv and use in dist lock unit tests
Branch: master
https://github.com/mongodb/mongo/commit/5acceb49d017548b065a26fc4a8c62e9638cfa45

Comment by Githook User [ 25/Jun/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-19115 Change CatalogManager unit tests to launch futures in a way that will clean up properly on failure
Branch: master
https://github.com/mongodb/mongo/commit/5303c54abcbba921e4a1a30628c3ab67f23df35b

Generated at Thu Feb 08 03:49:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.