[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:
Depends
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: SERVER-43261 Archive more libfuzzer artifacts in Evergreen
Branch: master
https://github.com/mongodb/mongo/commit/c650690d1e43b3863b88e237378444e723e42d80

Comment by Mark Benvenuto [ 24/Sep/19 ]

Code Review URL: https://mongodbcr.appspot.com/504890010/

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