[SERVER-25548] resmoke should not continue after a shell crash Created: 10/Aug/16  Updated: 09/Sep/20  Resolved: 25/Jun/20

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.3.10
Fix Version/s: 4.4.1, 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Raiden Worley (Inactive)
Resolution: Done Votes: 0
Labels: stm, tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: STM 2020-06-29, STM 2020-07-13
Participants:
Linked BF Score: 13
Story Points: 2

 Description   

Currently, resmoke stops the test if a mongo server has crashed in job.py. We should have it do the same for a shell crash.

For suites that use the shell to spawn servers, a shell crash would cause the servers to not be terminated. Subsequent tests will then run on servers from previous tests, causing either test failures or hangs.

Having these additional failures defeat the purpose of running with continueOnFailure.



 Comments   
Comment by Githook User [ 06/Aug/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-25548 resmoke should not continue after a shell crash
Branch: v4.4
https://github.com/mongodb/mongo/commit/0fa1bb77e760a5356b522393063319df9aea23a8

Comment by Githook User [ 25/Jun/20 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-25548 resmoke should not continue after a shell crash
Branch: master
https://github.com/mongodb/mongo/commit/4f4e1bd9702d7cd49b8358803f305ab7151917e3

Generated at Thu Feb 08 04:09:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.