[SERVER-61415] Hang analyzer won't signal python processes when the python process isn't named python Created: 11/Nov/21 Updated: 06/Feb/23 Resolved: 06/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Richard Samuels (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sdp-backlog-purge | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
Today I observed an issue with tausif.rahman where the hang analyzer would not pick up his locally running resmoke instance. When I asked him to modify the hang analyzer invocation copied from here targeted processes named python3 (instead of python), it was able to pick up resmoke. Both resmoke and the hang analyzer were invoked as ./buildscripts/resmoke.py .... To be clear, there are no known issues with this in the waterfall/Evergreen (where we explicitly invoke resmoke and the hanganalyzer as python), but this can affect local user experience. |