-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Cluster Scalability
-
ALL
txn_two_phase_commit_coordinator_shutdown_and_restart.js invokes a potentially asserting command through startParallelShell(), but it is not verifying its correct execution by checking the exit code of the spawned process.
As a consequence of this, any exception raised within the code section run in parallel won't be detected by resmoke/evergreen as a test failure - instead, the following will be logged:
[js_test:txn_two_phase_commit_coordinator_shutdown_and_restart] sh20176| uncaught exception: Error: command did not fail with any of the following codes [ 50 ] {
[js_test:txn_two_phase_commit_coordinator_shutdown_and_restart] sh20176| "ok" : 0,
[js_test:txn_two_phase_commit_coordinator_shutdown_and_restart] sh20176| "errmsg" : "Could not find host matching read preference { mode: \"primary\" } for set txn_two_phase_commit_coordinator_shutdown_and_restart-rs0",
(link to the occurrence: https://logkeeper.mongodb.org/lobster/build/9d6a13e85dbfb9cdaec07f4c61b0fddc/test/60e5348354f2481be6ee9219#bookmarks=0%2C7768%2C7770%2C11130&f~=000~sh%5Cd%2B%5C%7C).
This other test may be used as a reference for implementing a fix.
- is related to
-
SERVER-58200 Asserting clauses do not cause a jstest to fail when it is run through startParallelShell()
-
- Closed
-