We should do the same thing in smoke.py (in v3.0 and v2.6 branches) that resmoke does and not create new job objects if it's already running in one. That will allow us to use Evergreen's sophisticated process cleanup logic and remove pkill lines from evergreen.yml that clutter it up.
- is depended on by
-
SERVER-18727 Remove pkill lines from etc/evergreen.yml
- Closed
- related to
-
SERVER-17526 option to allow disabling job object creation in resmoke.py for win32
- Closed
-
SERVER-23946 Disable Evergreen Job Cleanup on 3.0 and 2.6 branches
- Closed
-
TOOLS-1605 Conditionally create a Windows job object in smoke.py
- Closed