ci: architecture-neutral jobs run on linux-arm64, balancing the two Linux pools #265

Merged
dcharlot merged 1 commit from ci/balance-linux-pools into main 2026-10-15 09:09:48 -04:00
Owner

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:

  • wai-http: its path gate, the falsify shards, the shard-coverage check, the corpus
    verified both ways with its differential, and the cache rules;
  • wai-pack: its path gate, the independent verifier, the floor through a media prober
    (ffmpeg from apt) and the dependency licences (cargo-deny);
  • wai-conformance: the v2 vocabulary, the independent verifiers, delivery telemetry
    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

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: - wai-http: its path gate, the falsify shards, the shard-coverage check, the corpus verified both ways with its differential, and the cache rules; - wai-pack: its path gate, the independent verifier, the floor through a media prober (ffmpeg from apt) and the dependency licences (cargo-deny); - wai-conformance: the v2 vocabulary, the independent verifiers, delivery telemetry 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](https://claude.com/claude-code)
ci: architecture-neutral jobs run on linux-arm64, balancing the two Linux pools
All checks were successful
WAI conformance / does this change touch it (pull_request) Successful in 11s
WAI HTTP delivery / WAI HTTP · does this change touch it (pull_request) Successful in 10s
wai-pack / wai-pack · does this change touch it (pull_request) Successful in 12s
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 46s
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 17m53s
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 2m17s
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 2m17s
wai-pack / wai-pack · macos (pull_request) Successful in 2m36s
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 25m25s
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 24m47s
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 1m12s
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 1m54s
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 2m24s
WAI HTTP delivery / HTTP corpus · falsify mutations 0/3 (pull_request) Successful in 1h2m38s
WAI HTTP delivery / HTTP corpus · falsify mutations 1/3 (pull_request) Successful in 1h0m55s
WAI HTTP delivery / HTTP corpus · falsify patches 0/3 (pull_request) Successful in 5m32s
WAI HTTP delivery / HTTP corpus · falsify patches 1/3 (pull_request) Successful in 6m26s
WAI HTTP delivery / HTTP corpus · falsify patches 2/3 (pull_request) Successful in 6m5s
WAI HTTP delivery / HTTP corpus · every patch and mutation in exactly one shard (pull_request) Successful in 4s
WAI HTTP delivery / HTTP corpus · verified both ways, and the differential (pull_request) Successful in 2m43s
WAI HTTP delivery / cache rules · controls and labelled caches (pull_request) Successful in 1m14s
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m23s
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 4m12s
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 22s
wai-pack / wai-pack · dependency licences (pull_request) Successful in 1m10s
WAI HTTP delivery / HTTP corpus · falsify mutations 2/3 (pull_request) Successful in 49m18s
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 2m4s
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 27s
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 9m0s
wai-pack / wai-pack · linux (pull_request) Successful in 1m32s
7e699e37c5
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:

- wai-http: its path gate, the falsify shards, the shard-coverage check, the corpus
  verified both ways with its differential, and the cache rules;
- wai-pack: its path gate, the independent verifier, the floor through a media prober
  (ffmpeg from apt) and the dependency licences (cargo-deny);
- wai-conformance: the v2 vocabulary, the independent verifiers, delivery telemetry
  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.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!265
No description provided.