Max Moroz
Max Moroz
@inferno-chromium suggested a nice solution on libFuzzer side (to print stats after reading the first corpus dir), I've uploaded a CL as https://reviews.llvm.org/D66020, but we probably need to chose some...
One more relevant problem: we don't use `-use_value_profile=1` during merge, that means we discard some features that could've been discovered during fuzzing. That explains why `new_features` stat so often has...
One more thing that came up during discussion with @jonathanmetzman today. With this new merge thing, we might want to do `gsutil cp` and `gsutil rm` after every fuzzing run,...
FTR, the most recent Clang roll in Chromium should include my `-merge=1` change, so that is not a blocker anymore, but there are still some other things that can delay...
I've checked BigQuery stats for the past 15 days for both Chromium ClusterFuzz and OSS-Fuzz. The change has definitely had an effect -- I can share stats with Googlers. One...
As per Abhishek's suggestion I've checked whether this new implementation affected the number of post-fuzzing merge timeouts. I've checked the logs for the past 7+ days and it looks like...
Re-evaluating some strategies / metrics after the change being deployed for ~2 weeks (access to the link is restricted for non-Googlers): 1) DFT on OSS-Fuzz: https://docs.google.com/spreadsheets/d/14hAEuRsfofSiInUTR7KA48SbGY4QPuxHOzObjVPInQk/edit#gid=1395928105 on average, DFT strategy...
> > One more relevant problem: we don't use -use_value_profile=1 during merge, that means we discard some features that could've been discovered during fuzzing. That explains why new_features stat so...
@sylvestre Hello! Yeah, I'm able to see Mozilla among the corporate signers, and in the worst case can just ignore the CLA check here. However, there is definitely a way...
thank you @sylvestre ! and in the meantime we're waiting for @@andreafioraldi to take a look