[SERVER-35036] Remove database and collection cleanup from $config.teardown functions Created: 17/May/18  Updated: 29/Oct/23  Resolved: 13/Jun/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.0.0-rc6, 4.1.1

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: David Bradford (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-35197 Change CleanEveryN to CleanupConcurre... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: TIG 2018-06-04, TIG 2018-06-18
Participants:
Story Points: 3

 Description   

As mentioned in this comment of SERVER-34548, having FSM workloads drop their (unique) database or collection in the $config.teardown() function undermines our data consistency checks as the contents will be deleted before the resmoke.py hooks run. We should leave it to the CleanupConcurrencyWorkloads hook from SERVER-30204 to drop all the databases and collections after the data consistency checks run.



 Comments   
Comment by Githook User [ 13/Jun/18 ]

Author:

{'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}

Message: SERVER-35036: Remove individual concurrency test cleanups

(cherry picked from commit 0412c9a439cace2abcb019943f6abee319038fbd)
Branch: v4.0
https://github.com/mongodb/mongo/commit/527699b80481dba90e5b5aec386faa4b4aa20c86

Comment by Githook User [ 13/Jun/18 ]

Author:

{'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}

Message: SERVER-35036: Remove individual concurrency test cleanups
Branch: master
https://github.com/mongodb/mongo/commit/0412c9a439cace2abcb019943f6abee319038fbd

Generated at Thu Feb 08 04:38:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.