-
Notifications
You must be signed in to change notification settings - Fork 121
Open
Labels
blocked-on-rustBlocked on a Rust feature landing or stabilizingBlocked on a Rust feature landing or stabilizingcompatibility-nonbreakingChanges that are (likely to be) non-breakingChanges that are (likely to be) non-breaking
Description
Currently, Miri doesn't support any wasm target (see #22 (comment)). Once one is supported, we should run cargo miri test
on a wasm target in CI.
EDIT: This appears to also be true of riscv64gc-unknown-linux-gnu, although I haven't found it documented anywhere.
Old issue text
This job failed for reasons that seem specific to running cargo miri test
with the target set to wasm32-wasi
. I'm going to disable the test for the time being.
Thanks to @frazar for discovering rust-lang/miri#1916, which suggests that Miri lacks support for some wasm32 targets. The task for this issue now is to a) determine whether any wasm32 targets are supported, b) switch to using a supported one if so or, c) skip running Miri when targetting wasm32 if none are supported.
Metadata
Metadata
Assignees
Labels
blocked-on-rustBlocked on a Rust feature landing or stabilizingBlocked on a Rust feature landing or stabilizingcompatibility-nonbreakingChanges that are (likely to be) non-breakingChanges that are (likely to be) non-breaking