There doesn't seem to be an easy way to import existing corpora

[evverx]

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 about an hour trying to import a corpus I think the easiest way is to open a PR where the corpus is put in $OUT/fuzz-target_seed_corpus.zip and temporarily unblock cflite_batch to run it on PRs. This way, the corpus is uploaded and can be used by PRs before cflite_batch itself is merged.

[jonathanmetzman]

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 about an hour trying to import a corpus I think the easiest way is to open a PR where the corpus is put in $OUT/fuzz-target_seed_corpus.zip and temporarily unblock cflite_batch to run it on PRs. This way, the corpus is uploaded and can be used by PRs before cflite_batch itself is merged.

I suppose that would add to the repo size.
If you're using the git filestore then I think it's actually not so hard to add to an existing corpus right?

[evverx]

If you're using the git filestore then I think it's actually not so hard to add to an existing corpus right?

I didn't consider using a git repository to keep corpora because as far as I understand it isn't compatible with forks in the sense that every fork would have to create PERSONAL_ACCESS_TOKEN manually and change storage-repo accordingly.

[jonathanmetzman]

Interesting point.