[SERVER-82261] setup_spawnhost_coredump script may miss core dump from crashed process on Windows Created: 17/Oct/23 Updated: 25/Jan/24 Resolved: 07/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0, 7.0.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Matt Kneiser |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Build
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v7.2, v7.1, v7.0
|
||||
| Sprint: | Execution Team 2023-11-13 | ||||
| Participants: | |||||
| Description |
|
When we capture core dumps on Windows, there are two different ways they can be named: in the form of dump_mongod.7468.mdmp.gz or in the form of mongod.2023-09-18T13-17-41.mdmp.gz. The latter case is often the core dump of interest since it's from a crashed process. However, it appears that the setup_spawnhost_coredump script misses core dumps with this (latter) naming scheme and does not download/copy them over correctly. |
| Comments |
| Comment by Githook User [ 25/Jan/24 ] |
|
Author: {'name': 'Matt Kneiser', 'email': 'matt.kneiser@mongodb.com', 'username': 'themattman'}Message: GitOrigin-RevId: 884cf384fbb4e65ebd8432eefa688e401d9cf90e |
| Comment by Githook User [ 07/Nov/23 ] |
|
Author: {'name': 'Matt Kneiser', 'email': 'matt.kneiser@mongodb.com', 'username': 'themattman'}Message: |
| Comment by Trevor Guidry [ 17/Oct/23 ] |
|
Can you give an example task this happens with so we can reproduce this? |