[SERVER-46820] Kill hung processes as the last step in resmoke's signal handler Created: 12/Mar/20 Updated: 16/Sep/20 Resolved: 11/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vlad Rachev (Inactive) | Assignee: | Vlad Rachev (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | STM 2020-06-29 | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
After the signal handler has finished running the hang-analyzer, it will kill the hung processes, similarly to what archival does now. This is necessary to ensure resmoke can make forward progress and shut itself down so that the evergreen agent does not timeout while waiting for resmoke processes to exit. Note that archival will still need to be able to shut down hung processes in the case that the test fails normally without timing out. |
| Comments |
| Comment by Brooke Miller [ 13/Mar/20 ] |
|
To test this, we'll send a signal to Resmoke and check that it eventually kills itself. The test should be in an infinite loop to ensure this happens. |