Bug#1051815: [Pkg-rust-maintainers] Bug#1051815: wasmedge - autopkgtest failure with rustc 1.68
> Peter Green hat am 13.09.2023 05:24 CEST geschrieben: > On 12/09/2023 23:30, Faidon Liambotis wrote: > > Control: reassign -1 rustc 1.68.2+dfsg1-1 > > Control: retitle -1 Builds invalid wasm32 binaries (1.67->1.68 regression) > > > > On Tue, Sep 12, 2023 at 10:56:57PM +0100, Peter Green wrote: > >> The autopkgtests for wasmedge fail with rustc 1.68, I have observed this > >> with > >> both testing and unstable's versions of wasmedge, and with both testing and > >> unstable's versions of wasi-lib. > > Thanks for the report. Actually, I think the WasmEdge autopkgtests are > > catching a rustc 1.68 regression, whereas rustc compiles wasm32 binaries > > that do not work with neither WasmEdge, nor Wasmtime (the latter is not > > in Debian). > And it seems the issue persists with rustc 1.69 :( > > https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37797497/log.gz this is most likely a regression in wasi-libc (it just got exposed once rustc switched to the new version). the last version enabled stack protection since upstream allegedly supports that now, seems it's still broken and I'll revert that change and report back.
Bug#1051815: wasmedge - autopkgtest failure with rustc 1.68
On 12/09/2023 23:30, Faidon Liambotis wrote: Control: reassign -1 rustc 1.68.2+dfsg1-1 Control: retitle -1 Builds invalid wasm32 binaries (1.67->1.68 regression) On Tue, Sep 12, 2023 at 10:56:57PM +0100, Peter Green wrote: The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with both testing and unstable's versions of wasmedge, and with both testing and unstable's versions of wasi-lib. Thanks for the report. Actually, I think the WasmEdge autopkgtests are catching a rustc 1.68 regression, whereas rustc compiles wasm32 binaries that do not work with neither WasmEdge, nor Wasmtime (the latter is not in Debian). And it seems the issue persists with rustc 1.69 :( https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37797497/log.gz Very simple test case: $ podman run --rm -it debian:sid # or bookworm to test with rustc 1.67 root@ad697f1c195f:~# apt install rustc libstd-rust-dev-wasm32 [...] root@ad697f1c195f:~# rustc -V rustc 1.68.2 root@ad697f1c195f:~# cat > hello.rs
Bug#1051815: wasmedge - autopkgtest failure with rustc 1.68
Control: reassign -1 rustc 1.68.2+dfsg1-1 Control: retitle -1 Builds invalid wasm32 binaries (1.67->1.68 regression) On Tue, Sep 12, 2023 at 10:56:57PM +0100, Peter Green wrote: > The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with > both testing and unstable's versions of wasmedge, and with both testing and > unstable's versions of wasi-lib. Thanks for the report. Actually, I think the WasmEdge autopkgtests are catching a rustc 1.68 regression, whereas rustc compiles wasm32 binaries that do not work with neither WasmEdge, nor Wasmtime (the latter is not in Debian). Very simple test case: $ podman run --rm -it debian:sid # or bookworm to test with rustc 1.67 root@ad697f1c195f:~# apt install rustc libstd-rust-dev-wasm32 [...] root@ad697f1c195f:~# rustc -V rustc 1.68.2 root@ad697f1c195f:~# cat > hello.rs
Processed: Re: Bug#1051815: wasmedge - autopkgtest failure with rustc 1.68
Processing control commands: > reassign -1 rustc 1.68.2+dfsg1-1 Bug #1051815 [wasmedge] wasmedge - autopkgtest failure with rustc 1.68 Bug reassigned from package 'wasmedge' to 'rustc'. No longer marked as found in versions wasmedge/0.13.3+dfsg-1. Ignoring request to alter fixed versions of bug #1051815 to the same values previously set Bug #1051815 [rustc] wasmedge - autopkgtest failure with rustc 1.68 Marked as found in versions rustc/1.68.2+dfsg1-1. > retitle -1 Builds invalid wasm32 binaries (1.67->1.68 regression) Bug #1051815 [rustc] wasmedge - autopkgtest failure with rustc 1.68 Changed Bug title to 'Builds invalid wasm32 binaries (1.67->1.68 regression)' from 'wasmedge - autopkgtest failure with rustc 1.68'. -- 1051815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051815: wasmedge - autopkgtest failure with rustc 1.68
Package: wasmedge Version: 0.13.3+dfsg-1 Severity:serious The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with both testing and unstable's versions of wasmedge, and with both testing and unstable's versions of wasi-lib. https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37793933/log.gz https://ci.debian.net/data/autopkgtest/unstable/amd64/w/wasmedge/37778163/log.gz https://ci.debian.net/data/autopkgtest/testing/amd64/w/wasmedge/37770138/log.gz 93s autopkgtest [14:54:23]: test capi-wasi-env: [--- 93s 1..2 94s ok 1 build wasi_get_env.wasm with cargo/rustc 94s not ok 2 build set_wasm_env with gcc 94s # (in test file debian/tests/capi-wasi-env, line 24) 94s # `assert_output --partial "ENV1: VAL1"' failed 94s # 94s # -- output does not contain substring -- 94s # substring (1 lines): 94s # ENV1: VAL1 94s # output (4 lines): 94s # [2023-09-12 14:54:24.910] [error] execution failed: unreachable, Code: 0x89 94s # [2023-09-12 14:54:24.910] [error] In instruction: unreachable (0x00) , Bytecode offset: 0x9efb 94s # [2023-09-12 14:54:24.910] [error] When executing function name: "print_env" 94s # Execution Failed. Error message: unreachable 94s # -- 94s # 95s autopkgtest [14:54:25]: test capi-wasi-env: ---] 95s autopkgtest [14:54:25]: test capi-wasi-env: - - - - - - - - - - results - - - - - - - - - - 95s capi-wasi-envFAIL non-zero exit status 1
