alexcrichton
commented
10 months ago Hello! Currently all continuous fuzzing is done through oss-fuzz which up-to-now has only supported x86_64 for Wasmtime. We haven't planned or designed what it might look like to continuously run fuzzing elsewhere on different hardware, it's always been a reach goal for us in that regard. That being said if you're willing to help out here that would be great!
The rough idea for what we have in mind is something oss-fuzz-like where it continuously fuzzes over time and rebuilds on a nightly basis. Ideally it'd include things like automatic regression finding and test case reduction, but starting out with continuous fuzzing and reporting issues is, in my opinion, probably the best first step.
Unfortunately we don't have a piece of software along the lines of "take this and run this and that's all that's needed". There's a fair bit of infrastructural work here but I'd be happy to discuss in more detail if you'd like.
Hi,
In order to help the wasmtime project, we would like to fill the missing Tier1 requirement for the target aarch-unknown-linux-gnu.
Currently, we are able to set up continuous fuzzing of wasmtime on aarch64/linux platform. We are just seeking your guidance as to the steps and process needed to complete this task.
Our team has found this github repo about wasmtime fuzzing, could you please confirm it has all the necessary information:
https://github.com/bytecodealliance/wasmtime/blob/main/fuzz/README.md
If you could please let us know if there are additional details on how we can fulfill this requirement on the aarch64 platform, we would appreciate it.
Warm regards,
Manoj Dahal Sartura CC @lperkov @jvijtiuk