[SERVER-75801] Core dumps missing after fassert failure Created: 06/Apr/23  Updated: 29/Oct/23  Resolved: 07/Apr/23

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: George Wangensteen Assignee: Alex Neben
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Development Platform
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Sometimes, core dumps appear to be missing from artifacts after an fassert-failure calls std::abort. This is true even when the evergreen task-logs mention that they are enabling core dumps. 



 Comments   
Comment by Githook User [ 07/Apr/23 ]

Author:

{'name': 'Alexander Neben', 'email': 'alexander.neben@mongodb.com', 'username': 'IamXander'}

Message: SERVER-75801 Added correct tsan options for core dumps
Branch: master
https://github.com/mongodb/mongo/commit/e3631d6d9e746d22726f8237e2dc9b03708f9efe

Comment by Alex Neben [ 07/Apr/23 ]

Getting merged right now

Comment by Alex Neben [ 06/Apr/23 ]

In every task we try to upload core dumps (regardless if they have been taken). I don't see anything in the logs were we actually do the core dump. Is this functionality we had or is this a brand new feature?

Comment by Max Hirschhorn [ 06/Apr/23 ]

I bumped this ticket to P2 because as a policy I believe Server engineers shouldn't receive BF tickets / Evergreen failures which don't have useful diagnostics attached to them. In some cases the failure itself is undebuggable from only the logs.

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