[SERVER-53779] Hang analyzer should more robustly identify candidate processes Created: 14/Jan/21  Updated: 06/Dec/22

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

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) 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

Assigned Teams:
Server Tooling & Methods
Backwards Compatibility: Fully Compatible
Participants:

 Description   

In SERVER-50852, unit tests were renamed to end uniformly with _test, and then linting enforcement was added in SERVER-51692. However, this shouldn't be a long term solution: the hang analyzer could use other sources of data (binaries in install/bin, or unit test lists generated by the build system) to form a more robust list of candidates. Developers should have freedom to name tests as they see fit. As part of doing this work, the lint restrictions introduced in SERVER-51692 should be reverted.



 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.

Comment by Robert Guo (Inactive) [ 10/Dec/21 ]

Backlogging this since we're not moving the hang analyzer out of the server repo. I think it's still nice to do when we revisit tickets with the tig-hanganalyzer label

Comment by Robert Guo (Inactive) [ 19/Jan/21 ]

This makes sense. We're going to work on it after reworking the integration with evergreen.yml. There's a substantial amount of shell for unittest archiving in evergreen.yml already that makes debugging and iterating difficult.

Generated at Thu Feb 08 05:31:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.