Closed vivekvpandya closed 1 year ago
When running fuzz test in CI with cargo-fuzz it takes lots of time. Can lots of output log on console be reason for that? Is it possible to reduce logs and only get information about things when fuzzer finds some test failure?
This output is produced by libfuzzer, not cargo fuzz, so it would be better to bring it up with upstream.
cargo fuzz
For your CI issues, you can pipe it into a file, perhaps, and then tail the file on failure.
When running fuzz test in CI with cargo-fuzz it takes lots of time. Can lots of output log on console be reason for that? Is it possible to reduce logs and only get information about things when fuzzer finds some test failure?