Stream: git-wasmtime

Topic: wasmtime / issue #10000 Spurious (?) CI failures on s390x

view this post on Zulip 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-cli crate:

The first was re-queued and merged and the second is currently back in the queue. The first didn't touch anything in wasmtime-cli and 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

view this post on Zulip 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?

view this post on Zulip Wasmtime GitHub notifications bot (Jan 16 2025 at 17:38):

abrown added the cranelift:area:s390x label to Issue #10000.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 05 2025 at 00:04):

abrown commented on issue #10000:

Not sure, but I believe I saw a similar failure over in #10110: https://github.com/bytecodealliance/wasmtime/actions/runs/13124822832/job/36618948362#step:18:987.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 19 2025 at 20:38):

alexcrichton commented on issue #10000:

Another failure at https://github.com/bytecodealliance/wasmtime/actions/runs/13421426149/job/37494891337

Last updated: Feb 28 2025 at 03:10 UTC