Max Moroz
Max Moroz
c#47 hints that the initial reproducer might've been unreliable / failing to reproduce on Stable. I'll check the logs.
I've uploaded another testcase from that bug. It has been processed correctly: https://clusterfuzz.com/testcase-detail/5742515649314816 Also nothing suspicious in the logs for the original testcase (https://clusterfuzz.com/testcase-detail/5740292802412544). I've exported all the logs into...
coming from gradientfuzz, so I'm suspecting Marty might've deployed / enabled something?
Yes! Will start in November
I'm thinking for large testcases (e.g. more than 10KBs) we could try to allocate up to an hour? But don't want to spend that much for smaller things :/
Sorry I still didn't get to it. Wanted to gather some data on how long we need to minimize depending on the size of the input, and didn't have time...
was there a CL landed to address this? The intention was to parse the logs for the `INFO: found LLVMFuzzerCustomMutator` string to make sure the mutator library was actually used
@ravi50041 thank you for trying out this functionality and for reaching out with questions. It'll help us to improve that page / workflow. > i have per fuzzer json file....
Action items for us to improve the docs: * [ ] Clarify `project_name` value
> so I should use temp as project name to upload the coverage data right ? No. The project can be specified in either job description (via `PROJECT_NAME` env variable)...