[SERVER-32469] Improve logging of GDB commands in hang_analyzer.py Created: 27/Dec/17  Updated: 06/Dec/22

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

Type: Improvement Priority: Minor - P4
Reporter: Max Hirschhorn Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Unresolved Votes: 0
Labels: move-sdp-candidate, tig-hanganalyzer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Server Tooling & Methods
Participants:
Linked BF Score: 15

 Description   

We've previously observed the "timeout" phase of the etc/evergreen.yml project configuration getting stuck and hitting the 15-minute time limit. SERVER-27158 was a change to resmoke.py to reduce the sheer number of processes we'd have running towards the end of an Evergreen task; however, there remain cases where GDB itself is getting stuck. We should add additional logging in hang_analyzer.py to display the command and its arguments prior to it being run (e.g. by using GDB's echo command) so we have a better idea of where the issue is coming from in the future.

Note: GDB doesn't support a logging mode where it not only logs the output of the command but also the command itself. https://sourceware.org/bugzilla/show_bug.cgi?id=8822



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

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