Spurious (?) CI failures on s390x

[alexcrichton]

I've seen two CI builds fail today on the s390x tests of the wasmtime-cli crate:

• https://github.com/bytecodealliance/wasmtime/actions/runs/12752790805/job/35543074991 (Improve some logging in the differential fuzzer #9982 (comment))
• https://github.com/bytecodealliance/wasmtime/actions/runs/12755184456/job/35550742014 (pulley: Add more addressing modes for loads/stores #9994 (comment))

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

[iii-i]

In my local runs I've seen segfaults due to an ABI problem in the capstone wrapper: capstone-rust/capstone-rs#166. I wonder if this can be related?

[abrown]

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.

[alexcrichton]

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

[alexcrichton]

another

[alexcrichton]

another

[alexcrichton]

another