-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.5.13
-
Component/s: Sharding, Testing Infrastructure
The check that UUIDs are consistent across a cluster was placed in ShardingTest.stop() under SERVER-30511.
It was intended to provide passthrough coverage that UUIDs are always consistent in a cluster, by running at the end of every test that starts a ShardingTest.
However, only tests that actually call ShardingTest.stop() will perform the check.
Should we:
- audit all jstests to ensure they call ShardingTest.stop() if they start a ShardingTest
- place some kind of lint or compile check to ensure any future tests call ShardingTest.stop() if they start a ShardingTest?
- duplicates
-
SERVER-25640 Have ReplSetTest run checkDBHashes() in stopSet()
- Closed
- related to
-
SERVER-43522 Complete TODO listed in SERVER-31226
- Closed