|
Not an expert on the mutational fuzzer, but sharding tests don't seem to be filtered out by the fuzzer:
$ npm run jstestfuzz -- --jsTestsDir /home/ubuntu/mongo/jstests/ -d
|
...
|
[2021-09-16T11:44:09.123Z debug] Searching for files and directories in /home/ubuntu/mongo/jstests/sharding
|
[2021-09-16T11:44:09.130Z debug] Searching for files and directories in /home/ubuntu/mongo/jstests/sharding/query
|
[2021-09-16T11:44:09.131Z debug] Searching for files and directories in /home/ubuntu/mongo/jstests/sharding/load_balancer_support
|
[2021-09-16T11:44:09.131Z debug] Searching for files and directories in /home/ubuntu/mongo/jstests/sharding/libs
|
[2021-09-16T11:44:09.131Z debug] Searching for files and directories in /home/ubuntu/mongo/jstests/sharding/change_streams
|
...
|
So I believe that our renameCollection tests are considered as inputs. Then I guess that it will depend on the transformations performed by the jstestsfuzzer that we end up testing the environment described above (rename/new DDL path over a sharded collection + jstestsfuzz_sharded_continuous_stepdown).
|