[SERVER-19824] Mongo shell should report that subprograms exited with non-zero exit code if they die … Created: 06/Aug/15  Updated: 25/Jan/17  Resolved: 12/Aug/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.1.7

Type: Bug Priority: Critical - P2
Reporter: Atul Kachru Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-18474 provide core dump on fassert and inva... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 7 08/10/15
Participants:
Linked BF Score: 0

 Description   

Linux 64 replication failure: https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_replication_39239a2ef13ea814dd06617ce5642f067dac89bc_15_08_06_19_35_18

Linux 64 replication_wt:
https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_replication_WT_39239a2ef13ea814dd06617ce5642f067dac89bc_15_08_06_19_35_18

replication_auth:
https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_replication_auth_39239a2ef13ea814dd06617ce5642f067dac89bc_15_08_06_19_35_18

Test summary:
https://evergreen.mongodb.com/task_history/mongodb-mongo-master/replication?#/master1.js=fail



 Comments   
Comment by Githook User [ 12/Aug/15 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-19824 Make mongo shell report a non-zero exit code for subprograms that die.

This patch causes wait_for_pid to report that processes that terminate due to a signal had a non-zero exit code. Specifically, it reports -1 times the signal number.
Branch: master
https://github.com/mongodb/mongo/commit/ff7b100090712d75bd619bb3a4b9664feea7238b

Comment by Andy Schwerin [ 07/Aug/15 ]

The root of the problem is that the mongo shell erroneously reports an exit code of 0| for processes that terminate with a signal. See here.

Generated at Thu Feb 08 03:52:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.