ci: architecture-neutral jobs run on linux-arm64, balancing the two Linux pools #265
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/balance-linux-pools"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ci: architecture-neutral jobs run on linux-arm64, balancing the two Linux pools
On 2026-10-15 the one x86_64 runner (linux, two slots) had about 104 jobs queued while
the linux-arm64 runner on the build host sat idle. Thirteen of the jobs pinned to
linux need nothing x86_64: every tool they use comes through rustup, pip, apt, npm or
cargo install, which pick the host's architecture, and nothing they check depends on
it. They now run on linux-arm64:
verified both ways with its differential, and the cache rules;
(ffmpeg from apt) and the dependency licences (cargo-deny);
against an independent library, and C2PA emission.
The wasm32-wasip2 quantum job stays on linux: it pins an x86_64 wasmtime archive and
refuses any other host. The Kani shard stays too. Byte-equality and cross-architecture
legs keep both labels, as before. The three workflows parse; the concurrency check
passes. This change runs them in full, on their new runner, before it merges.
🤖 Generated with Claude Code