mirror of
https://github.com/apache/superset.git
synced 2026-05-30 04:39:20 +00:00
44244fc377
The multi-platform `docker-build (websocket)` job on master has been flaking ~13% with `exit code: 132` (SIGILL) during `npm ci && npm run build` on the `linux/arm64` leg. The `linux/amd64` leg always succeeds on the same host, so the trigger is QEMU's user-mode x86_64→aarch64 translator mis-executing one of the instructions a newer Node native module postinstall emits. `docker/setup-qemu-action@v3.6.0` is itself pinned, but it pulls `tonistiigi/binfmt:latest` by default — a moving target. Pin the binfmt image to `tonistiigi/binfmt:qemu-v8.1.5` (a recent, broadly-used QEMU release) so the emulator binaries stop drifting under us. This is a CI-only change. Output image bytes are unchanged: cross-built amd64/arm64 artifacts are identical regardless of which QEMU version emulates the build. Affects all four workflows that consume `./.github/actions/setup-docker` (docker.yml, tag-release.yml, showtime-trigger.yml, ephemeral-env.yml) — same emulator gets registered for all of them; for amd64-only workflows the registration is a no-op.