Wasmtime GitHub notifications bot (Mar 24 2024 at 22:40): Wasmtime GitHub notifications bot (Mar 24 2024 at 22:40):cfallin requested wasmtime-core-reviewers for a review on PR #8230.
Wasmtime GitHub notifications bot (Mar 24 2024 at 22:40):cfallin opened PR #8230 from cfallin:on-second-thought-lets-not-fuzz-pcc-its-a-silly-idea to bytecodealliance:main:
There have been more fuzzbugs than expected and the onslaught of issues something I definitely don't have time to deal with right now; let's try again later in the year (unless someone else wants to drive this!).
This puts the fuzzing logic under an off-by-default feature so it can still be tested and developed in-tree as desired.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Mar 24 2024 at 22:40):cfallin requested alexcrichton for a review on PR #8230.
Wasmtime GitHub notifications bot (Mar 24 2024 at 22:41):cfallin edited PR #8230:
There have been more fuzzbugs than expected and the onslaught of issues is something I definitely don't have time to deal with right now; let's try again later in the year (unless someone else wants to drive this!).
This puts the fuzzing logic under an off-by-default feature so it can still be tested and developed in-tree as desired.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Mar 24 2024 at 22:44):github-actions[bot] commented on PR #8230:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "fuzzing"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Wasmtime GitHub notifications bot (Mar 25 2024 at 02:07):jameysharp submitted PR review:
Aw, that's too bad. I hope we can take the time to figure out more of this soon.
Wasmtime GitHub notifications bot (Mar 25 2024 at 04:57):cfallin merged PR #8230.
Last updated: Dec 23 2024 at 12:05 UTC