[SERVER-17526] option to allow disabling job object creation in resmoke.py for win32 Created: 10/Mar/15  Updated: 27/Apr/16  Resolved: 29/May/15

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

Type: Bug Priority: Major - P3
Reporter: Michael O'Brien Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-1424 smoke.py could use some work Closed
is depended on by SERVER-18727 Remove pkill lines from etc/evergreen... Closed
Related
is related to SERVER-23959 option to allow disabling job object ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Quint Iteration 3.1.2, Quint Iteration 3, Quint Iteration 4
Participants:

 Description   

smoke.py creates a job object when spawning processes, so that it can reliably terminate everything when finished.

however this means that in CI tasks we can't use job objects, because the processes spawned by smoke.py already belong to a job, so it will trigger a failure.



 Comments   
Comment by Max Hirschhorn [ 29/May/15 ]

Filed SERVER-18727 to remove the pkill lines that should be unnecessary now.

Comment by Githook User [ 29/May/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-17526 Enable tracking of spawned processes in MCI.

On Windows, this will cause MCI to assign processes to a job object.
Change resmoke.py to only create a job object if the current process
is not already assigned to one.
Branch: master
https://github.com/mongodb/mongo/commit/6b41043ce9f0866de48732ddbbe49d66d4027d85

Comment by Michael O'Brien [ 08/May/15 ]

max.hirschhorn@10gen.com yes - try making a patch, and in the patched evergreen.yml add this command to the "pre" section:

- command: shell.track

and add this to the end of the "post" section

- command: shell.cleanup

The first command should create a job object, and add every subsequent process spawned by shell.exec to the job object. The last command will then terminate the job object that it started in pre. Hopefully that should do it.

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