Stream: git-wasmtime

Topic: wasmtime / issue #10823 Nocapture option has assertion fa...

Wasmtime GitHub notifications bot (May 22 2025 at 03:10):

jlb6740 opened issue #10823:

@alexcrichton @abrown

Testing in the new assembler fails when no capture is passed --nocapture
cd cranelift/assembler-x64
cargo test -- --nocapture

Test executable failed (exit status: 101).

stderr:

thread 'main' panicked at /home/jlbirch/wasmtime-jlb6740-for-assembler-dev/cranelift/assembler-x64/src/fixed.rs:45:9:
assertion failed: self.0.enc() == E
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I tracked down that the error started occurring after this patch was merged:
https://github.com/bytecodealliance/wasmtime/pull/10806

Note, there is no assertion error when the

--nocapture

option is omitted.

Wasmtime GitHub notifications bot (May 22 2025 at 14:32):

alexcrichton commented on issue #10823:

I think you're seeing the output of this test which is supposed to panic. Is this failing tests for you locally? While --nocapture shows the message the exit code of cargo test -- --nocapture is still 0 for me

Wasmtime GitHub notifications bot (May 22 2025 at 18:20):

jlb6740 closed issue #10823:

@alexcrichton @abrown

Testing in the new assembler fails when no capture is passed --nocapture
cd cranelift/assembler-x64
cargo test -- --nocapture

Test executable failed (exit status: 101).

stderr:

thread 'main' panicked at /home/jlbirch/wasmtime-jlb6740-for-assembler-dev/cranelift/assembler-x64/src/fixed.rs:45:9:
assertion failed: self.0.enc() == E
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I tracked down that the error started occurring after this patch was merged:
https://github.com/bytecodealliance/wasmtime/pull/10806

Note, there is no assertion error when the

--nocapture

option is omitted.

Wasmtime GitHub notifications bot (May 22 2025 at 18:20):

jlb6740 commented on issue #10823:

@alexcrichton Looks like this is running the doctest you highlight and the test comments does say it should panic but this doc test is not new but the panic is (at least on my platform). Yes the exit code is still 0. I will close this. Perhaps the cargo update that had to do once I rebased against patch https://github.com/bytecodealliance/wasmtime/pull/10806, changed the behavior of this test for me. Will close.

Wasmtime GitHub notifications bot (May 22 2025 at 18:21):

jlb6740 edited a comment on issue #10823:

@alexcrichton Looks like this is running the doctest you highlight and the test comments does say it should panic but the confusion for me was this doctest was not new, while the panic was (at least on my platform). Yes the exit code is still 0. Perhaps the cargo update that had to do once I rebased against patch https://github.com/bytecodealliance/wasmtime/pull/10806, changed the behavior of this test for me. I will close this.

Wasmtime GitHub notifications bot (May 22 2025 at 18:27):

jlb6740 edited a comment on issue #10823:

@alexcrichton Looks like this is running the doctest you highlight and the test comments does say it should panic but the confusion for me was this doctest was not new, while the panic was (at least on my platform). Yes the exit code is still 0. Perhaps the cargo update that had to be done once I rebased against patch https://github.com/bytecodealliance/wasmtime/pull/10806, changed the behavior of this test for me. I will close this.

Last updated: Dec 06 2025 at 06:05 UTC