Wasmtime GitHub notifications bot (Jan 13 2025 at 20:34): Wasmtime GitHub notifications bot (Jan 13 2025 at 20:34):alexcrichton opened issue #10000:
I've seen two CI builds fail today on the s390x tests of the
wasmtime-clicrate:
- https://github.com/bytecodealliance/wasmtime/actions/runs/12752790805/job/35543074991 (https://github.com/bytecodealliance/wasmtime/pull/9982#event-15909676078)
- https://github.com/bytecodealliance/wasmtime/actions/runs/12755184456/job/35550742014 (https://github.com/bytecodealliance/wasmtime/pull/9994#event-15912281849)
The first was re-queued and merged and the second is currently back in the queue. The first didn't touch anything in
wasmtime-cliand the second does touch quite a bit that could affect it so it's currently an assumption of mine that the s390x-failure there was specific to s390x.I tried running the test suite in a loop locally for a bit using s390x/qemu and so far it hasn't failed in the same way. I figured I'd open an issue to keep track of things if they happen in the future.
cc @uweigand
Wasmtime GitHub notifications bot (Jan 16 2025 at 13:34):iii-i commented on issue #10000:
In my local runs I've seen segfaults due to an ABI problem in the capstone wrapper: https://github.com/capstone-rust/capstone-rs/pull/166. I wonder if this can be related?
Wasmtime GitHub notifications bot (Jan 16 2025 at 17:38):abrown added the cranelift:area:s390x label to Issue #10000.
Last updated: Jan 24 2025 at 00:11 UTC