[SERVER-77891] Use 'optional' flag to s3.get to acquire libfuzzer corpus Created: 07/Jun/23  Updated: 14/Nov/23  Resolved: 14/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Task Priority: Minor - P4
Reporter: Spencer Jackson Assignee: Spencer Jackson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-76852 Allow libfuzzer tasks in Evergreen to... Closed
Assigned Teams:
Server Security
Backwards Compatibility: Fully Compatible
Sprint: Security 2023-11-13, Security 2023-11-27
Participants:

 Description   

libfuzzer may use a corpus of prior findings to accelerate its fuzzing. Unfortunately, Evergreen did not allow s3.get to optionally acquire an artifact off of S3, to allow the first iteration to run on a branch to bootstrap. Instead we implemented a workaround in SERVER-76852, which is messy and possibly prone to failure in the future.

Evergreen intends to implement a parameter to s3.get called "optional" which should resolve this issue more permanently in EVG-19801. We should adopt this flag, and revert the changes made to our setup_group, when we are able to.



 Comments   
Comment by Githook User [ 14/Nov/23 ]

Author:

{'name': 'Spencer Jackson', 'email': 'spencer.jackson@mongodb.com', 'username': 'spencerjackson'}

Message: SERVER-77891 Use 'optional' s3.get to fetch libfuzzer corpus
Branch: master
https://github.com/mongodb/mongo/commit/81643a517cfb93c413eb5a9adb6d0a7c240945c8

Generated at Thu Feb 08 06:36:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.