[SERVER-20484] Save diagnostic files on failure on Evergreen Created: 18/Sep/15 Updated: 29/Sep/16 Resolved: 29/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | TIG 9 (09/18/15) | ||||||||
| Participants: | |||||||||
| Description |
|
Saving the diagnostic files on mongod/mongos failure, as a build artifact in Evergreen, is helpful for debugging the failure. This has already been done for Windows, see |
| Comments |
| Comment by Robert Guo (Inactive) [ 29/Sep/16 ] |
|
jonathan.abrahams I'm going to close this ticket since it's mostly done. We added collecting FTDC and diskstats data in |
| Comment by Scott Hernandez (Inactive) [ 18/Sep/15 ] |
|
Is this about evergreen? If so, please clarify. |