[SERVER-54793] Delete core files if task is successful Created: 25/Feb/21 Updated: 29/Oct/23 Resolved: 29/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.7, 5.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Mikhail Shchatko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.4
|
||||
| Sprint: | STM 2021-04-05 | ||||
| Participants: | |||||
| Story Points: | 1 | ||||
| Description |
|
The unittest archival code uses the presence of core files to determine if binaries should be archived, since at least one test always generates a core file, we always archive the binaries. Instead, we should modify the resmoke caller to delete all unittest cores if the test succeeds |
| Comments |
| Comment by Githook User [ 12/May/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: (cherry picked from commit 5d6dd453f4c3d9c257a827085d7faad7174df63c) |
| Comment by Andrew Morrow (Inactive) [ 31/Mar/21 ] |
|
Are older branches affected by this? If so I'd propose that it would be good to backport, at least to v4.4. |
| Comment by Githook User [ 29/Mar/21 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: |