libfuzzer travis setup via cargo fuzz

[spacejam]

No description provided.

[anxiousmodernman]

Saw something that might be relevant on Reddit.
https://www.reddit.com/r/rust/comments/89y5eo/fuzzing_as_a_service_startup_looking_for_rust/?st=jfn060ji&sh=a3a747da

Is this the cargo fuzz you're talking about?

[spacejam]

@anxiousmodernman https://github.com/rust-fuzz/cargo-fuzz

[ehiggs]

Fuzzing isn't really a closed process. It has an unbounded time as the fuzzer keeps feeding new inputs. e.g. from @anxiousmodernman's reddit post:

For Rust projects, we did test against the Rust library for Cap'n Proto messages where we found a fairly obscure bug after ~2 weeks of fuzzing.

So I guess the intention here is to timebox the fuzzer for each build and hopefully the aggregate over many builds might find something?

[spacejam]

fuzzing is implemented, but you're right about it being more of a thing you kick to a spare server to run more or less continuously