fitzgen opened PR #10068 from fitzgen:no-winch-fuzzing-on-non-x86_64
to bytecodealliance:main
:
<!--
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
-->
fitzgen requested alexcrichton for a review on PR #10068.
fitzgen requested wasmtime-fuzz-reviewers for a review on PR #10068.
alexcrichton submitted PR review:
Thinking again about this, maybe add a
log::warn!
as well here? (I think we do that for CPU features where if one is requested and the local CPU doesn't have it we log to that effect)
alexcrichton commented on PR #10068:
Ah this is the warning I'm thinking of
github-actions[bot] commented on PR #10068:
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>
fitzgen updated PR #10068.
fitzgen has enabled auto merge for PR #10068.
fitzgen merged PR #10068.
Last updated: Jan 24 2025 at 00:11 UTC