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

wai-quantum: the members certified on the Mac Studio run on the Studio #537

Merged
dcharlot merged 1 commit from wai/quantum-members-on-the-studio into main 2026-10-29 16:38:03 -04:00
Conversation 0 Commits 1 Files changed 2 +7 -2
dcharlot commented 2026-10-29 14:34:46 -04:00
Owner
Copy link

Three new runners joined macos and linux on 2026-10-29: an M5 Max and an
M4 Max (both with the matrix extension, and other GPUs), and the iMac's Linux
VM. #533's run put two Studio-certified members on them:

  • member · Metal (macos), pinned to the Studio's gpu-msl-1009, ran on the
    M5 Max: every c0-c5 test failed, the device undeclared.
  • member · matrix extension absent (macos) ran on an M4 Max: "this runner
    has SME".

Both now ask for macos-m3-ultra, a label the Studio's runner carries beside
macos. The fleet's other macOS jobs stay on macos. Members for the
laptops' GPUs and their matrix extension are for a run on them to declare.

(The third failure, the riscv64 vector member on the iMac's VM, was the VM
lacking a riscv64 binfmt handler. That is fixed on the host: qemu-user 8.2.2's
handlers are installed there, as on jetson-hub.)

Merge order: the macos-m3-ultra label must be live on the Studio runner first (the owner runs studio-runner-label.sh); until then the two re-pinned jobs wait in the queue.

Public-name check: clean.

🤖 Generated with Claude Code

Three new runners joined `macos` and `linux` on 2026-10-29: an M5 Max and an M4 Max (both with the matrix extension, and other GPUs), and the iMac's Linux VM. #533's run put two Studio-certified members on them: - `member · Metal (macos)`, pinned to the Studio's gpu-msl-1009, ran on the M5 Max: every c0-c5 test failed, the device undeclared. - `member · matrix extension absent (macos)` ran on an M4 Max: "this runner has SME". Both now ask for `macos-m3-ultra`, a label the Studio's runner carries beside `macos`. The fleet's other macOS jobs stay on `macos`. Members for the laptops' GPUs and their matrix extension are for a run on them to declare. (The third failure, the riscv64 vector member on the iMac's VM, was the VM lacking a riscv64 binfmt handler. That is fixed on the host: qemu-user 8.2.2's handlers are installed there, as on jetson-hub.) **Merge order:** the `macos-m3-ultra` label must be live on the Studio runner first (the owner runs `studio-runner-label.sh`); until then the two re-pinned jobs wait in the queue. Public-name check: clean. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
wai-quantum: the members certified on the Mac Studio run on the Studio
All checks were successful
wai-quantum matrix-extension member / does this change touch it (pull_request) Successful in 8s
Details
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 11s
Details
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
Details
wai-quantum Metal member / does this change touch it (pull_request) Successful in 11s
Details
wai-quantum matrix-extension member / member · matrix extension, emulated (aarch64 Linux) (pull_request) Successful in 25s
Details
wai-quantum Metal member / member · Metal absent (linux) (pull_request) Successful in 52s
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m44s
Details
wai-quantum Metal member / member · Metal (macos) (pull_request) Successful in 7m34s
Details
wai-quantum matrix-extension member / member · matrix extension absent (macos) (pull_request) Successful in 10m11s
Details
2d6cb8274a 
Three new runners joined `macos` and `linux` on 2026-10-29: an M5 Max and an
M4 Max (both with the matrix extension, and other GPUs), and the iMac's Linux
VM. #533's run put two Studio-certified members on them:
- `member · Metal (macos)`, pinned to the Studio's gpu-msl-1009, ran on the
  M5 Max: every c0-c5 test failed, the device undeclared.
- `member · matrix extension absent (macos)` ran on an M4 Max: "this runner
  has SME".

Both now ask for `macos-m3-ultra`, a label the Studio's runner carries beside
`macos`. The fleet's other macOS jobs stay on `macos`. Members for the
laptops' GPUs and their matrix extension are for a run on them to declare.

(The third failure, the riscv64 vector member on the iMac's VM, was the VM
lacking a riscv64 binfmt handler. That is fixed on the host: qemu-user 8.2.2's
handlers are installed there, as on jetson-hub.)

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!537
No description provided.