[SERVER-65351] Spike: Run the symbolizer on shell fixtures Created: 07/Apr/22 Updated: 06/May/22 Resolved: 19/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Jeffrey Zambory | Assignee: | Mikhail Shchatko |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | DAG 2022-04-18, DAG 2022-05-02 | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 0 | ||||||||||||
| Description |
|
Currently, the stacktraces shown in Evergreen's logs are not very useful for mongodb-mongo-.* projects. This is due to the fact that these tracktraces are created without symbols and so do not contain very actionable debug information. We should integrate the symbolizer into how we run tests in Evergreen so that we can automatically symbolize any stacktraces that are created. This will allow Server engineers to more easily debug any failures in their tests. ------------------------ As a Server engineer, I want to see symbolized tracktraces in my Evergreen logs, so that I can easily debug my failures. ------------------------ AC:
TImebox: 2-3 days |
| Comments |
| Comment by Iryna Zhuravlova [ 11/Apr/22 ] |
|
We decided to make this ticket a Spike with a time box around 2-3 days for investigation. We will recap on the POA after Misha completes this investigation |