-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:None
-
Fully Compatible
-
STM 2020-06-29, STM 2020-07-13, STM 2020-07-27
-
2
The patch now allows the following command line invocations:
resmoke run --replayFile foo.txt
and
resmoke run @foo.txt
If the contents of foo.txt are:
jstests/concurrency/fsm_workloads/indexed_insert_multikey.js jstests/concurrency/fsm_workloads/indexed_insert_2dsphere.js
the invocation is analogous to:
resmoke run jstests/concurrency/fsm_workloads/indexed_insert_multikey.js jstests/concurrency/fsm_workloads/indexed_insert_2dsphere.js
Thus other command line flags such as --suite still take effect.
Also noteworthy, resmoke will run the contents of the replay file in the order they are listed. Repeated test files will be run once per repetition; prior behavior was to dedup test files.
Original ticket:
When running a set of tests with resmoke, one has the option of running them in alphabetical order or totally random. It would be nice if the random runs could at least use a deterministic order when provided a seed.
The goal here is to also be compatible with using --jobs=N. The jobs flag will partition the test suite into different runners. When providing a seed, the each runner should deterministically run the same tests in the same order.