bytecodealliance / bytecodealliance/wasmtime

Spurious (?) CI failures on s390x

Open
#10,000 27 comments 0 reactions 0 assignees View on GitHub
ci cranelift:area:s390x
Dominant language
Rust
Stars
18.6k
Forks
1.8k
Avg merge
1d 18h
Merged PRs (30d)
126

Description

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 (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-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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.