[SERVER-32195] Powercycle - Support remote stack dump of python process to a file Created: 06/Dec/17  Updated: 06/Dec/22  Resolved: 11/May/20

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

Type: Task Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: stm, tig-powercycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

The work for SERVER-32074 added support to dump the python stacks when a signal (or Windows event) was received in powertest.py. This signal (or event) is triggered by the hang_analyzer when a timeout condition occurs. The resulting output is stdout, for that python process (and not the hang_analyzer). In the case of a remote process, it needs to be dumped to a file, i.e., debugger_remote_python_<pid>.log, which is similar to the mongod log produced by the hang_analyzer. Following this convention, the timeout phase of evergreen.yml will automatically copy the remote file over and be archived with the timed out task.



 Comments   
Comment by Ryan Timmons [ 11/May/20 ]

Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue.

Generated at Thu Feb 08 04:29:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.