[SERVER-71335] Debug symbols of server binaries used by system_perf.yml are archived in S3 Created: 14/Nov/22 Updated: 29/Oct/23 Resolved: 27/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc5, 7.0.0-rc7, 4.4.24, 5.0.20, 6.0.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | James O'Leary |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v7.0, v6.3, v6.0, v5.0, v4.4
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 35 | ||||||||||||
| Description |
|
It is possible for sys-perf workloads to find correctness issues where the server crashes. Core dumps from these failure are successfully uploaded to S3 in the DSI Artifacts tarball. However, the debug symbols corresponding to the server binaries used are not uploaded to S3. This limitation makes the core dump of a lesser value. We should make a change to ensure the debug symbols are archived to S3. One option is to stop using the --separate-debug option to avoid splitting the mongod executable into mongod and mongod.debug. Another option is to include the *.debug files by adding install-core-debug, install-jstestshell-debug, and install-mongocryptd-debug targets to the SCons invocation. |
| Comments |
| Comment by Githook User [ 05/Jul/23 ] |
|
Author: {'name': 'Jim O'\''Leary', 'email': 'jim.oleary@gmail.com', 'username': 'jimoleary'}Message: (cherry picked from commit ca6f9cab4f9a0f7dfae083468856af26b0a7aa53) |
| Comment by Githook User [ 05/Jul/23 ] |
|
Author: {'name': 'Jim O'\''Leary', 'email': 'jim.oleary@gmail.com', 'username': 'jimoleary'}Message: (cherry picked from commit ca6f9cab4f9a0f7dfae083468856af26b0a7aa53) |
| Comment by Githook User [ 05/Jul/23 ] |
|
Author: {'name': 'Jim O'\''Leary', 'email': 'jim.oleary@gmail.com', 'username': 'jimoleary'}Message: (cherry picked from commit ca6f9cab4f9a0f7dfae083468856af26b0a7aa53) |
| Comment by Githook User [ 05/Jul/23 ] |
|
Author: {'name': 'Jim O'\''Leary', 'email': 'jim.oleary@gmail.com', 'username': 'jimoleary'}Message: (cherry picked from commit ca6f9cab4f9a0f7dfae083468856af26b0a7aa53) |
| Comment by Githook User [ 27/Jun/23 ] |
|
Author: {'name': 'Jim O'\''Leary', 'email': 'jim.oleary@gmail.com', 'username': 'jimoleary'}Message: |
| Comment by James O'Leary [ 23/Jun/23 ] |
|
Pushed the previous updates to the correct repo. |
| Comment by Matthew Lewandowski [ 12/Dec/22 ] |
|
Moving this ticket out of Evergreen PLT's backlog. We believe this lives with Perf or SDP. Would like to help sheperd this ticket in any way we can. alexander.neben@mongodb.com Sending to you as a first step. |
| Comment by Annie Black [ 21/Nov/22 ] |
|
john.daniels@mongodb.com does this look like a PLT ticket? In which case we should move this ticket to EVG (or else remove Evergreen backlog as the assignee). |