As part of a PR review, I noticed that there are several callers of stopMongod where we are incorrectly passing our option as signal (which then gets interpreted as null).

stopMongod is defined with the signature:

MongoRunner.stopMongod(conn, signal, opts, waitpid)

where signal is expecting a number (defaulted as parseInt(signal) || SIGTERM) and opts is skipValidation etc. However we currently call stopMongod in a few places as:

MongoRunner.stopMongod(conn, {noCleanData: true});

Where the second argument becomes NaN which then signal interprets as SIGTERM and we silently ignore the options argument.

Go through existing stopMongod call sites and fix this.