[SERVER-42753] Ensure libfuzzer evergreen tasks always upload their corpus Created: 09/Aug/19 Updated: 29/Oct/23 Resolved: 13/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Reams | Assignee: | Jonathan Reams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Security 2019-08-12, Security 2019-08-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently the libfuzzer task uploads its corpus as a normal function in the task rather than part of the teardown tasks in the task group. This means that if libfuzzer fails, it doesn't upload its corpus to s3 afterwards - loosing all the information it gained during the failed run. |
| Comments |
| Comment by Githook User [ 13/Aug/19 ] |
|
Author: {'name': 'Jonathan Reams', 'email': 'jonathan.reams@mongodb.com'}Message: |