* ci: run fuzz tests in matrix
* ci: fail if fuzzing fails
* ci: rename fuzz step
* ci: clean up env
* ci: fix fuzz test target matching
* ci: prebuild fuzz corpus
* ci: collect coverage while running tests
Instead of running tests twice, we can just run them
once while collecting coverage data.
* ci: temporarily disable `reth-eth-wire` fuzzing
* ci: collect fuzz coverage data
* ci: fix fuzz coverage collection
* ci: re-enable `reth-eth-wire`
* move hello to separate file
* cargo fmt
* wip: actual fuzz test
* should probably also take advantage of test-fuzz to generate
benchmarks like impl_fuzzer_with_input
* impl generic roundtrip method
* generate test with macro
* change testname to fuzzname
* add reth-eth-wire to fuzz in ci
* add other message types to fuzz
* remove unused_crate_dependencies
* was causing test issues, may want to revisit whether or not we can
include this warning and still use test_fuzz
* more afl debugging ci
* use more explicit imports in fuzz_rlp
* impl Default for types and fuzz ping/pong
* Default is necessary for test-fuzz to auto generate a corpus for each
type we are fuzz testing
* enable AFL_I_DONT_CARE_ABOUT_MISSING_CRASHES
* not sure if we should do this in the workflow instead:
echo core >/proc/sys/kernel/core_pattern
we may miss crashes if we keep this enabled?
* remove reth-interfaces from fuzzing
* add secp256k1 to reth-db dev deps
