Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Security 2019-08-12, Security 2019-08-26
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.
Attachments
Issue Links
- causes
-
SERVER-42926 Fix path in libfuzzer evergreen task
-
- Closed
-
-
SERVER-42968 libfuzzer teardown tasks should be merged with compile's
-
- Closed
-