This patch changes the format of the TestData.setParameters variable we
pass to the mongo shell from within resmoke. We now pass this value as a
JavaScript object, where keys are parameter names and values are the
values to set for that parameter. Additionally, we also consolidate the
hard-coded 'logComponentVerbosity' default settings into resmoke, instead of
having them mixed between servers.js and resmoke's programs.py. Now, any
mongod processes started either directly by resmoke or via a mongo shell
that was started by resmoke will receive default log verbosity settings
from a value defined in resmoke.
When deleting the donor range after migrating a chunk off of a shard,
the range deleter will schedule the deletion at some time in the future,
according to a server parameter orphanCleanupDelaySecs, which defaults
to 900, or 15 minutes. It does not delay range deletions preparatory to
migrating a range in, and does not put off deleting the donor range if
the moveChunk command has set the option _waitForDelete.
The file jstests/sharding/write_commands_sharding_state.js had CR (0x0D)
line endings, which made the patch fail lint. The substantive changes
in the file were to add "_waitForDelete" options to the moveChunk
commands.
Forwards the value for resmoke.py's --numClientsPerFixture command line
option to the mongo shell running the test. This enables the fuzzer to
know if there are concurrent clients running the test.
Split out the passthrough tests into separate suites. The MongoDB
deployment is started up by resmoke.py so that we can record the
success/failure of each individual test in MCI.
Added support for parallel execution of tests by dispatching to
multiple MongoDB deployments.
Added support for grouping different kinds of tests (e.g. C++ unit
tests, dbtests, and jstests) so that they can be run together. This
allows for customizability in specifying what tests to execute when
changes are made to a particular part of the code.
