[SERVER-9608] Prevent smoke.py from killing running builds Created: 07/May/13 Updated: 11/Jul/16 Resolved: 26/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
If you have an ongoing build and run a test with smoke.py, smoke.py will kill the running build. This is especially annoying if you have a full test suite running for an extended period of time and are trying to work in parallel, as every new test run will kill any pending builds. |
| Comments |
| Comment by Githook User [ 26/Nov/13 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Eric Milkie [ 07/May/13 ] |
|
Yes, the way "shouldKill()" figures out what to kill is braindead. I've had emacs sessions get killed by this because I happened to start it with a file whose path matched what it looks for in the process name. It's ridiculous. |