[SERVER-65781] Have shell fixtures be symbolized Created: 19/Apr/22  Updated: 29/Oct/23  Resolved: 18/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.2, 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Jeffrey Zambory Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-72866 resmoke symbolizer service raises Pyt... Closed
related to SERVER-65351 Spike: Run the symbolizer on shell fi... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: DAG 2022-05-16, DAG 2022-05-30
Participants:
Story Points: 2

 Description   

Based on the results of the Spike ticket linked, we have two things to do before we can start adding symbolized stack traces to shell outputs in Evergreen.

  1. Fix the locking issue around how stacktraces were being found by the file system
  2. Add a 5 minute timeout to how long we wait to try to get symbols and symbolize stacktraces. If it takes longer than that, we gracefully fail the symbolizer and allow the task to continue

------------------------

As a Server engineer,

I want to see symbolized tracktraces in my Evergreen logs,

so that I can easily debug my failures.

------------------------

AC:

  • Symbolized stacktraces will be shown at the end of the test log they appear in
  • If we can't symbolize a task, we gracefully fail the symbolizer portion of the task and allow the task to continue on like normal


 Comments   
Comment by Githook User [ 18/May/22 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-65781 Run the symbolizer on CI output
Branch: master
https://github.com/mongodb/mongo/commit/ff674137736f6df1f74dd08267ef11c82e0e75d2

Generated at Thu Feb 08 06:03:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.