[SERVER-25726] Archive *.dmp files in Evergreen Created: 22/Aug/16  Updated: 02/Sep/16  Resolved: 22/Aug/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.3.12

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-24625 Monitor Silent Process Exit on Window... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: TIG 2016-08-29
Participants:

 Description   

A patch build that a) included the fix for SERVER-24625 and b) triggered an access violation on exit did not preserve minidump artifacts.

I think this is because *.dmp files are not being archived.



 Comments   
Comment by Githook User [ 22/Aug/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-25726 Archive *.dmp files in Evergreen
Branch: master
https://github.com/mongodb/mongo/commit/b95bc22f402524dd49dec267946e9726f2baa7cd

Comment by Kamran K. [ 22/Aug/16 ]

Here's the patch build referenced in the description: https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_sharding_last_stable_mongos_and_mixed_shards_e404756a317fbd531306805cf77e723b9c3fc218_16_08_19_16_26_19/0

In Robert's initial patch set for SERVER-24625, the .dmp files were archived. I'm not sure why the include pattern was removed in follow-up patch sets.

Generated at Thu Feb 08 04:10:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.