[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: |
|
||||||||||||||||||||
| 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 |
| 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: On Windows, this will cause MCI to assign processes to a job object. |
| 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. |