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.