[SERVER-58325] Failures in txn_two_phase_commit_coordinator_shutdown_and_restart.js may go undetected by resmoke/Evergreen Created: 07/Jul/21  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Paolo Polato Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-58200 Asserting clauses do not cause a jste... Closed
Assigned Teams:
Cluster Scalability
Operating System: ALL
Participants:

 Description   

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.


Generated at Thu Feb 08 05:44:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.