t/00_diag.t ......... ok
t/alien_wasmtime.t .. 1/? #
#
#
# Alien::wasmtime->cflags = -I/home/ollisg/dev/Alien-wasmtime/.build/XjoGeBWR7R/blib/lib/auto/share/dist/Alien-wasmtime/include
# Alien::wasmtime->cflags_static = -I/home/ollisg/dev/Alien-wasmtime/.build/XjoGeBWR7R/blib/lib/auto/share/dist/Alien-wasmtime/include
# Alien::wasmtime->install_type = share
# Alien::wasmtime->libs = -L/home/ollisg/dev/Alien-wasmtime/.build/XjoGeBWR7R/blib/lib/auto/share/dist/Alien-wasmtime/lib -lwasmtime
# Alien::wasmtime->libs_static = -L/home/ollisg/dev/Alien-wasmtime/.build/XjoGeBWR7R/blib/lib/auto/share/dist/Alien-wasmtime/lib -lwasmtime
# Alien::wasmtime->version = 0.22.1
# Alien::wasmtime->dynamic_libs = /home/ollisg/dev/Alien-wasmtime/.build/XjoGeBWR7R/blib/lib/auto/share/dist/Alien-wasmtime/lib/libwasmtime.so
#
#
thread '<unnamed>' panicked at 'assertion failed: res.eax == 0', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/raw-cpuid-8.1.2/src/lib.rs:295:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
t/alien_wasmtime.t .. All 3 subtests passed
Looks like this was fixed in rust-cpuidhttps://github.com/gz/rust-cpuid/issues/45. Unfortunately we are pulling older binaries from the wasmtime project and can't update until Wasm.pm is updated to work with the newer versions of wasmtime. It may also be possible to build our own binaries as a stop gap. I haven't seen this before and I am guessing the trigger is the newer CPU that I am now using in my new system.
plicease
commented
1 year ago
Looks like this was fixed in
rust-cpuidhttps://github.com/gz/rust-cpuid/issues/45. Unfortunately we are pulling older binaries from the wasmtime project and can't update until Wasm.pm is updated to work with the newer versions of wasmtime. It may also be possible to build our own binaries as a stop gap. I haven't seen this before and I am guessing the trigger is the newer CPU that I am now using in my new system.