-
Notifications
You must be signed in to change notification settings - Fork 199
Adding option to merge all inputs at once #282
Conversation
Can 'merge' be it's on template, rather than part of the existing libfuzzer template? |
What if I want to minimize corpus using "merge", what would be the best approach? I'm running these commands to minimize corpus. mkdir empty_dir
azcopy sync {container} ./corpus
./fuzzer -merge=1 ./empty_dir ./corpus
azcopy sync ./empty_dir {container} --deleteDestination=true I'm wondering if I can use this new merge task for this purpose. I imagine this might be one way:
But then, some other process should wait for the task to be completed and run the copy step. |
@tunz you will be able to use this task for that purpose. i am adding a new option to the libfuzzer template that will allow you to do this with this command.
|
@chkeita Thanks for the new option :) This will helps us a lot. |
@tunz you are correct. You will need to manually copy the result of the merge from the unique_inputs container. |
I think it's reasonable to optionally support merging into the inputs container, especially if we're talking about performing in a bulk fashion. |
Something important to remember, However, it's common enough to say "ok, this is a known good binary, minimize my corpus such that I can use the minimized set moving forwards" without having manual effort |
Standard integration tests pass, though I've not tested the new merge job. |
No description provided.