> We've used to have testdata in the repository, and used that data as a seed corpus for fuzz targets, but 10 months ago the tests have been deleted: https://codereview.chromium.org/2435373002
Sorry that I didn't know that fuzzer was using test/testdata.
If necessary, I can add them back (either entire source/test or just source/test/testdata). With gerrit, it's not any more an issue to have them back (I deleted them because I kept having riedvelt issues when updating ICU).
Would it work for fuzzer or do you still need seed_corpus/* ?
> https://github.com/Maluuba/icu/blob/master/source/test/testdata/test3.ucm
This is not a good example, I'm afraid. It's an encoding converter definition file.
Returning the testdata back would be fine as well. We just need to have it in the repo and specify a valid path to the directory in seed_corpus attribute (i.e. the stuff we temporarily removed in https://chromium-review.googlesource.com/c/600488)
Would it be possible to filter out bad examples and upload only "good" ones?
Comment 1 by js...@chromium.org
, Aug 3 2017