Stream: git-wasmtime

Topic: wasmtime / issue #13963 assert_malformed succeeds on well...

Wasmtime GitHub notifications bot (Jul 24 2026 at 19:52):

lukewagner opened issue #13963:

For example, this WAST test succeeds when I think it should fail:

(assert_malformed
  (component quote
    "(import \"f\" (func $f))"
  )
  "nothing wrong")

Wasmtime GitHub notifications bot (Jul 24 2026 at 19:52):

lukewagner added the bug label to Issue #13963.

Wasmtime GitHub notifications bot (Jul 24 2026 at 22:57):

alexcrichton commented on issue #13963:

I'd expect that component to expand to (component (import "f" (func $f))) which I thought was valid, but which part are you expecting to be invalid?

Wasmtime GitHub notifications bot (Jul 27 2026 at 00:29):

lukewagner commented on issue #13963:

Yes, agreed that component should be valid, but then I think the overall WAST test should fail (b/c it says assert_malformed), and atm it seems to silently succeed.

Wasmtime GitHub notifications bot (Jul 27 2026 at 20:57):

alexcrichton commented on issue #13963:

Ah, yes! Should be fixed in https://github.com/bytecodealliance/wasmtime/pull/14001

FWIW assert_malformed vs assert_invalid are more principled in the wasm-tools crate itself, right now in Wasmtime the two aren't separated out. In that sense component-model tests might want to run both wasm-tools wast and wasmtime wast. Not a great situation per-se though and we should probably just bring wasmtime wast up-to-par with wasm-tools wast

Wasmtime GitHub notifications bot (Jul 28 2026 at 19:36):

alexcrichton closed issue #13963:

For example, this WAST test succeeds when I think it should fail:

(assert_malformed
  (component quote
    "(import \"f\" (func $f))"
  )
  "nothing wrong")

Last updated: Jul 29 2026 at 05:03 UTC