jonathanmetzman
jonathanmetzman
libFuzzer doesn't really do well at continuing fuzzing after a crash. And using deduplication here goes against the "lite" philosophy behind CFLite. So if we were to continue fuzzing it...
> I'm not sure it can be fixed easily in the sense that it seems to be hard to upload artifacts using `curl` or something like that but having spent...
Interesting point.
Is this still a problem?
Will look at this when I come back from vacation.
I'll take a look at this next week when I get back from break.
> Looking at https://github.com/evverx/libbpf/actions/runs/1727948413, it seems artifacts uploaded by CFLite in PRs don't contain the names of fuzz targets either: > > ``` > $ unzip -l crashes-bpf-object-fuzzer_2.zip > Archive:...
> In https://github.com/evverx/libbpf/actions/runs/1728290427 the first "pruning" job uploaded a file named `crashes-bpf-object-fuzzer`: > > ``` > $ unzip -l crashes-bpf-object-fuzzer.zip > Archive: crashes-bpf-object-fuzzer.zip > Length Date Time Name > ---------...
> 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...
> 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...