https://roc-lang.github.io/roc-compiler-fuzz/
Clicking on the top entry (iphone) takes me to 404:
https://github.com/roc-lang/roc/blob/e3f3714d7bf9aec537a137f2934c1966b30f8a56/src/fuzz-parse.zig
Looks like a Luke branch, maybe transient. Or bad path to fuzz-parse.zig
Also: the bottom of src/README.md says Overview, then broken link: https://camo.githubusercontent.com/ddd54d7d0d304761ee604e07b0efc6442a83b6a90f8ffaad64acea7a1277e69c/68747470733a2f2f616e746f6e2d342e6769746875622e696f2f726f632d636f6d70696c65722d7669732f7a69675f646570656e64656e63795f67726170682e77656270
I found https://github.com/roc-lang/roc/tree/main/test/fuzzing
Sorry, im on iphone w one finger typing
I don't see the nature of the failure anywhere. I can click the coverage field, but iphone thinks phone number. I can't click e.g. "12 crashes"
Is the path to the fuzz script set in GHA?
Luke showed on the meeting to copy/paste the fuzz cmd and run locally. I don't have a terminal, but Id like to improve the fuzzing web ui. Maybe show the failure like traditional CI, but maybe this is less sensible for fuzzing results
That sounds like a good idea
We should be able to capture the verbose fuzz failure output and report it
I see a few action items:
Now that I have a terminal and keyboard available, I can start with manually running the fuzz commands and pick up more context that way. but happy to try to run with any of the 3 above as well
The code is fuzzers, CI jobs, and some zig code to generate the website. Pretty simple and fast to start up on bar fuzzing dependencies
You can work on the website using the checked in fuzzing data, but might need to expand it with more data for some of this work.
Earlier today I fixed the snapshot tool for generating a seed corpus using our snapshots. It did support the REPL type snapshots.
https://github.com/roc-lang/roc/pull/9110 for reference
Last updated: Feb 20 2026 at 12:27 UTC