Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
v4.0
-
TIG 2018-06-04, TIG 2018-06-18
-
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.
Attachments
Issue Links
- depends on
-
SERVER-35197 Change CleanEveryN to CleanupConcurrencyWorkloads in concurrency_replication_causal_consistency suite
-
- Closed
-