s2n-tls icon indicating copy to clipboard operation
s2n-tls copied to clipboard

Published 20 hours ago • verified publisher icon aws

Move Fuzz Corpuses to S3

Open zz85 opened this issue 5 years ago • 3 comments

Problem:

Currently fuzz corpuses reside in ./tests/fuzz/corpus/ and clutters pull requests, git history and objects.

Proposed Solution:

Move fuzz corpuses to S3 or a separate repository. This also allow corpuses can also be updated through a continuously integrated script.

zz85 avatar Jan 20 '20 19:01 zz85

Corpus files are being written to s3, left todo is

  • create an s3 retention policy
  • script the import of s3 corpus files into codebuild runs
  • remove corpus files from the repo (?)

dougch avatar Apr 27 '20 18:04 dougch

Alternatively EFS might be cheaper/faster/better due to not having to move corpus files around.

dougch avatar Jul 06 '20 17:07 dougch

Alternatively EFS might be cheaper/faster/better due to not having to move corpus files around.

Nope. VPC/auth issues add significant ops overhead handled more elegantly by s3.

dougch avatar Nov 18 '20 19:11 dougch

Done in #4665 and #4678

jouho avatar Aug 08 '24 22:08 jouho