Problem

The following resmoke suites run a ShardedClusterFixture but their names do not indicate they use a sharded cluster:

• causally_consistent_jscore_passthrough.yml
• causally_consistent_jscore_passthrough_auth.yml

This breaks the established naming convention where suites running on a sharded cluster include sharded_, sharding_, or mongos in their name (e.g. sharding_jscore_passthrough_base, sharded_causally_consistent_jscore_passthrough).

Proposed fix

Rename the suites using the sharding_ prefix, which by convention indicates a sharded cluster environment where collections are not implicitly sharded (as opposed to sharded_ which implies collections are sharded via implicitly_shard_accessed_collections.js):

Note: all references to these suite names in Evergreen configuration and any other build infrastructure will need to be updated accordingly.