Info
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.
Top User Comments
xgen-internal-githook commented on Fri, 7 Apr 2023 16:33:48 +0000:
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
JIRAUSER1268551 commented on Fri, 7 Apr 2023 15:33:23 +0000:
Getting merged right now
JIRAUSER1268551 commented on Thu, 6 Apr 2023 18:00:13 +0000:
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?
max.hirschhorn@10gen.com commented on Thu, 6 Apr 2023 17:32:10 +0000:
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.
