[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:
Problem/Incident
causes SERVER-42926 Fix path in libfuzzer evergreen task Closed
causes SERVER-42968 libfuzzer teardown tasks should be me... Closed
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: SERVER-42753 Upload libfuzzer corpus as teardown task
Branch: master
https://github.com/mongodb/mongo/commit/862995e019c7655a558fc926ba24a1780c55ec8d

Generated at Thu Feb 08 05:01:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.