[SERVER-83373] Antithesis sanity check should upload MongoDB Server logs to S3 on task failure Created: 16/Nov/23 Updated: 02/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Build
|
||||
| Participants: | |||||
| Linked BF Score: | 60 | ||||
| Description |
|
One challenge in debugging BF-30854 was a lack of diagnostics Server engineers are familiar with receiving on Evergreen task failure such as the mongod logs and data files. The archival feature built into resmoke cannot be used for external fixtures and so the antithesis* Evergreen tasks must take care to upload these diganostics to S3 and attach the metadata to the Evergreen tasks themselves. |