There doesn't seem to be a way to exclude corpora from artifacts about clusterfuzzlite HOT 7 OPEN

I think we can accomplish what you are asking for by allowing you to set FILESTORE=no_filestore (should be an easy fix) and by using #93

from clusterfuzzlite.

I'm not sure why corpora are included in those artifacts in the first place. I think it would probably make sense to always remove all the "*_seed_corpus.zip" files before uploading them.

from clusterfuzzlite.

I'm not sure why corpora are included in those artifacts in the first place. I think it would probably make sense to always remove all the "*_seed_corpus.zip" files before uploading them.

How much does this matter to you? I don't want to add too many smart features like this since it will add too much complexity

from clusterfuzzlite.

Those corpora take up about 400Mb (when they are compressed) and that's just too much I think. I can't upload huge artifacts like that on every commit (given that they are kept for 3 months by default).

from clusterfuzzlite.

Those corpora take up about 400Mb (when they are compressed) and that's just too much I think. I can't upload huge artifacts like that on every commit (given that they are kept for 3 months by default).

I'm going to try to fix this retention policy issue.
Lemme send a PR deleting the seed corpora.

from clusterfuzzlite.

@jonathanmetzman on second thought given that the size of those corpora can be controlled by scripts running on PRs I don't think they should be even uploaded. It took some time and I kind of DOSed myself with the public OSS-Fuzz corpora accidentally but it's possible to just open a PR, replace "code_change" with "batch" and put giant files in "$OUT/" to somewhat speed up this process. I still have no idea why GitHub allows that with read-only tokens but it is what it is apparently.

from clusterfuzzlite.

I can't seem to wrap my head around it. I think if it was possible to set FILESTORE=no_filestore without #93 it should do as well. I think I'd need #93 if I used the "batch" mode but I use only the "code-chage" mode and additionally am planning to turn on continuous builds.

from clusterfuzzlite.