-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
STM 2019-04-22
-
10
-
1
Sending a SIGTERM to resmoke.py causes the Python process to immediately exit (it doesn't register a handler for that signal like the server does) without waiting for any of the mongo shell processes it spawned to also exit (though they also receive the SIGTERM signal). This means if resmoke.py was in the midst of spawning a mongo shell process to run an FSM workload, then it could continue to run (i.e. be leaked) even after the parent resmoke.py process exits.
- is caused by
-
SERVER-35852 Convert backup_restore.js blacklist to use a YAML based list for transaction tests
- Closed
- related to
-
SERVER-40702 resmoke.py should wait for subprocesses it spawned to exit on KeyboardInterrupt
- Closed