[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: |
|
||||||||||||
| 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 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: |