Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

ci: the script-only checks run on the arm64 runner #245

Merged
dcharlot merged 1 commit from ci/checks-on-arm64 into main 2026-10-14 03:44:40 -04:00
Conversation 0 Commits 1 Files changed 5 +23 -8
dcharlot commented 2026-10-14 01:40:50 -04:00
Owner
Copy link

Moves the script-only CI checks from the linux runner to linux-arm64.

Why. The fleet has one x86_64 runner (linux), which runs every Rust workspace's tests. When measured it had 90 jobs waiting, against 14 for linux-arm64 and 9 for macos. Every pull request also queued its quick checks there, behind those builds.

What moves. Every job of five workflows that read files and run scripts, where the CPU architecture does not matter:

  • lockfiles (installs rustup, which supports arm64);
  • tests-in-ci;
  • workflow-hygiene;
  • no-vanity-metrics (four jobs);
  • wai-section-refs (uses setup-python, which has arm64 builds).

Nothing else changes. Each file says why at its jobs: line.

Evidence. These workflows run on this pull request itself (each fires on changes to its own file, or has no path filter), so their results here are their first runs on linux-arm64. The concurrency check passes with the edited files.

🤖 Generated with Claude Code

Moves the script-only CI checks from the `linux` runner to `linux-arm64`. **Why.** The fleet has one x86_64 runner (`linux`), which runs every Rust workspace's tests. When measured it had 90 jobs waiting, against 14 for `linux-arm64` and 9 for `macos`. Every pull request also queued its quick checks there, behind those builds. **What moves.** Every job of five workflows that read files and run scripts, where the CPU architecture does not matter: - `lockfiles` (installs rustup, which supports arm64); - `tests-in-ci`; - `workflow-hygiene`; - `no-vanity-metrics` (four jobs); - `wai-section-refs` (uses `setup-python`, which has arm64 builds). Nothing else changes. Each file says why at its `jobs:` line. **Evidence.** These workflows run on this pull request itself (each fires on changes to its own file, or has no path filter), so their results here are their first runs on `linux-arm64`. The concurrency check passes with the edited files. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ci: the script-only checks run on the arm64 runner
All checks were successful
lockfiles / every Cargo.lock is current (pull_request) Successful in 38s
Details
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 4s
Details
no-vanity-metrics / WAI public text names no comparison (pull_request) Successful in 4s
Details
no-vanity-metrics / WAI public text names no company or product (pull_request) Successful in 4s
Details
no-vanity-metrics / No new orphan source files (pull_request) Successful in 6s
Details
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 2m53s
Details
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m26s
Details
standards workspaces build + test / aac-rs (pull_request) Successful in 2m45s
Details
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 56s
Details
standards workspaces build + test / map-rs (pull_request) Successful in 58s
Details
standards workspaces build + test / mesh-rs (pull_request) Successful in 56s
Details
tests in CI / every test file is run by a job or listed with its reason (pull_request) Successful in 5s
Details
WAI section references / cited sections exist (pull_request) Successful in 25s
Details
workflow hygiene / every workflow supersedes its own queue (pull_request) Successful in 4s
Details
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 48s
Details
standards workspaces build + test / openpay (pull_request) Successful in 3m2s
Details
standards workspaces build + test / macOS energy backends (pull_request) Successful in 4m40s
Details
spec citations resolve / Code cites no section its SPEC lacks (pull_request) Successful in 4s
Details
standards workspaces build + test / arl-rs (pull_request) Successful in 1m9s
Details
standards workspaces build + test / eoc-rs (pull_request) Successful in 2m7s
Details
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m44s
Details
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 1m10s
Details
standards workspaces build + test / joulehook-rs (pull_request) Successful in 1m11s
Details
standards workspaces build + test / proof-rs (pull_request) Successful in 1m37s
Details
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m29s
Details
standards workspaces build + test / sense-rs (pull_request) Successful in 1m9s
Details
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m47s
Details
77eb5cad0f 
lockfiles, tests-in-ci, workflow-hygiene, no-vanity-metrics and
wai-section-refs read files and run scripts, so the CPU architecture does not
matter to them. They ran on the one x86_64 runner, which has every Rust
workspace's tests queued on it (90 jobs waiting when this was measured);
they move to linux-arm64.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!245
No description provided.