lukewagner opened issue #12352:
Running this command on the current
devrelease of wasmtime:wasmtime wast -W component-model-async=y -W component-model-async-builtins=y -W component-model-threading=y -W component-model-async-stackful=y -W exceptions=y wasmtime/*.wast wasm-tools/*.waston the main branch of the component-model repo in the
testdirectory currently crashes with this message:thread 'main' (639680) panicked at crates/wast/src/wast.rs:569:13: assertion failed: prev.is_none()Running
wasmtime/*.wastorwasm-tools/*.wastindependently passes, so it's some interaction between the tests in both directories that seems to cause the failure.
lukewagner added the bug label to Issue #12352.
alexcrichton assigned alexcrichton to issue #12352.
alexcrichton commented on issue #12352:
Should be fixed in https://github.com/bytecodealliance/wasmtime/pull/12358, thanks for reporting! We unfortunately don't have great coverage of the multi-file form of
wasmtime wastwhich is probably how this leaked through
alexcrichton closed issue #12352:
Running this command on the current
devrelease of wasmtime:wasmtime wast -W component-model-async=y -W component-model-async-builtins=y -W component-model-threading=y -W component-model-async-stackful=y -W exceptions=y wasmtime/*.wast wasm-tools/*.waston the main branch of the component-model repo in the
testdirectory currently crashes with this message:thread 'main' (639680) panicked at crates/wast/src/wast.rs:569:13: assertion failed: prev.is_none()Running
wasmtime/*.wastorwasm-tools/*.wastindependently passes, so it's some interaction between the tests in both directories that seems to cause the failure.
Last updated: Jan 29 2026 at 13:25 UTC