[SERVER-79906] Integrate resmoke core dump processing with the setup_spawnhost_coredump script Created: 10/Aug/23 Updated: 12/Nov/23 Resolved: 31/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Trevor Guidry | Assignee: | Trevor Guidry |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Right now we have this setup_spawnhost_coredump script that is not well maintained. We should try and reuse any resmoke code for analyzing core dumps that we can to help free us from some maintenance burden . |
| Comments |
| Comment by Trevor Guidry [ 31/Oct/23 ] |
|
After completion of https://jira.mongodb.org/browse/SERVER-80303 the spawnhost script now uses a gdb-index-cache and there are not many similarities with the core analyzer functions so this ticket does not make much sense.
I do want to make some overall improvements to the spawnhost script to make spawnhosts easier to use in general but I am waiting on completion of https://jira.mongodb.org/browse/DEVPROD-632 for that so we do not accidentally break anything. |