Closed netrome closed 1 month ago
It would be nice to verify somehow that if fuzzers fails, it will report about it. Could you try to introduce a bug in a separate PR which fuzzer will catch, please?=)
We had some fun doing this in this PR. Posting here for visibility: https://github.com/FuelLabs/fuel-vm/pull/846
@netrome Hi! Would you be open to chat about how this works our for Fuel in a few months from now?
@netrome Hi! Would you be open to chat about how this works our for Fuel in a few months from now?
Sure thing, I'd be happy to. Right now we're experiencing some issues with empty coverage uploads https://github.com/FuelLabs/fuel-fuzzing-corpus/commit/bf288985f3b94e8048d36b457c750cf7af6865b5 is that anything you recognize from other projects?
@netrome Hi! Would you be open to chat about how this works our for Fuel in a few months from now?
Sure thing, I'd be happy to. Right now we're experiencing some issues with empty coverage uploads FuelLabs/fuel-fuzzing-corpus@bf28898 is that anything you recognize from other projects?
Sadly does not ring a bell for me :/
Sadly does not ring a bell for me :/
Oh well, we'll figure it out.
Supersedes https://github.com/FuelLabs/fuel-vm/pull/727
This PR introduces fuzzing in our CI using ClusterFuzzLite, roughly following the instructions outlined in the ClusterFuzzLite Github Actions docs.
Before requesting review