[SERVER-43261] Archive more libfuzzer artifacts in Evergreen Created: 11/Sep/19 Updated: 29/Oct/23 Resolved: 26/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 2019-10-07 | ||||
| Participants: | |||||
| Linked BF Score: | 95 | ||||
| Description |
|
If libfuzzer emits artifacts, they should be tarred up and stored in S3 for the task. Any fuzzer binaries which were used to produce these artifacts should be stored as well, for later reproduction. |
| Comments |
| Comment by Githook User [ 25/Sep/19 ] |
|
Author: {'name': 'Mark Benvenuto', 'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com'}Message: |
| Comment by Mark Benvenuto [ 24/Sep/19 ] |
|
Code Review URL: https://mongodbcr.appspot.com/504890010/ |