testDDLDoNotProduceConsistencies in jstests/core_sharding/ddl/check_metadata_consistency_basic.js uses hardcoded collection names "coll" and "coll2" in the test database. In suites that share a cluster across tests, a prior test may leave test.coll behind as a timeseries collection. The subsequent shardCollection("test.coll", {_id: 1}) then fails with Location5914001 ("only the time field or meta field can be part of shard key pattern").

This failure was observed on v8.0 staging ( BF-43143 ). On master the issue is currently masked by the CleanEveryN enhancement from SERVER-94991 (v8.1+), which drops all user databases between tests, but it is better to make the test more robust by construction instead of relying on hook behavior for isolation.

Replace the hardcoded names with jsTestName() + "_1" / jsTestName() + "_2" so the collections are unique to this test file and cannot collide with state left behind by other tests in the suite.