Delete the component-async fuzzer#13223
Merged
alexcrichton merged 1 commit intobytecodealliance:mainfrom Apr 28, 2026
Merged
Conversation
This fuzzer was added in bytecodealliance#12119 with the hope of being a strong vector of fuzzing the component-model-async implementation. In the interim, however, we've discovered: * This fuzzer has found no issues. * Issues like bytecodealliance#13196 have happened, but they're bugs in `wit-bindgen`, not Wasmtime. * Many issues have been discovered which this fuzzer did not uncover. * This fuzzer takes a long time and special care to run due to needing to compile a large module at startup. Overall it just doesn't seem like this is pulling its weight. Designing a full fuzzer for component-async work I feel would need to start from scratch. I don't actually know how to build a fuzzer to discover the latent issues we've found via review/testing myself, but I'm hopeful someone in the future can be more clever than I. Closes bytecodealliance#13196
pchickey
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fuzzer was added in #12119 with the hope of being a strong vector of fuzzing the component-model-async implementation. In the interim, however, we've discovered:
wit-bindgen, not Wasmtime.Overall it just doesn't seem like this is pulling its weight. Designing a full fuzzer for component-async work I feel would need to start from scratch. I don't actually know how to build a fuzzer to discover the latent issues we've found via review/testing myself, but I'm hopeful someone in the future can be more clever than I.
Closes #13196