clusterfuzz
clusterfuzz copied to clipboard
also catch rust error messages that have been caught and resumed
This, in particular, should make fuzzers built with cargo-bolero able to get the proper error message auto-detected, rather than a generic abort.
PS: Hopefully this should be small enough to not require a CLA, as I am contributing on behalf of my employer and the process to get a CLA signed would be long for no reason. If you do need a CLA even for the smallest contributions, please feel free to let me know and I’ll see what I can do. But also don’t hesitate to do the change yourselves as though this were just a bug report, I’m just opening this to make your life simpler.
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.
Turns out the CLA process was easier than I expected, so that’s now done. AFAICT the remaining CI check is just someone from google needing to look at the PR, so I can’t do anything about it.
We do require a CLA but I think I can probably make this contribution myself.
/gcbrun
Could you add a test?
I just added a test by copy-pasting the test contents from our clusterfuzz UI, and ./local/tests/ci_tests.bash seems to pass, so hopefully this will be good to go :)
@jonathanmetzman Not sure whether you saw, but this is I think ready for review round 2 :)
@jonathanmetzman I don’t want to bother you so I’ll try just one last ping, I think this is ready for review :)
Anyway, thank you for the work you do on clusterfuzz, and hope this can help, whenever you manage to get to it!
/gcbrun
Welp seems like I don’t have permission to run this. Anyway, what I can say for sure is, ./local/tests/ci_tests.bash
passes locally :)
Actually, a thought: would it be better to get the line and char out of the summary? I’d just need to end the regex at :
instead of end-of-line; and it might help with clusterfuzz automatically detecting that it’s the same fuzzer crash. OTOH, if it doesn’t actually help clusterfuzz detect that, then it’s probably better to just leave it, as it makes reading the crash easier.