Skip to content

ci: build and test GPUI desktop on Intel macOS - #2698

Merged
richiemcilroy merged 1 commit into
mainfrom
ci/gpui-intel-macos
Oct 19, 2026
Merged

richiemcilroy merged 1 commit into
mainfrom
ci/gpui-intel-macos

Conversation

@richiemcilroy

@richiemcilroy richiemcilroy commented Oct 18, 2026 •

Copy link
Copy Markdown
Member

A nightly crashed for a user on an Intel Mac (MacBookPro16,3, macOS 15, x86_64). CI only builds and tests the GPUI app on Apple Silicon, Windows and Linux, so nothing catches breakage that only shows up on x86_64 macOS before a release ships it. The Intel release build is cross-compiled on an Apple Silicon runner, so its code never actually runs anywhere in CI.

What this adds:

  • A x86_64-apple-darwin entry in the Build GPUI Desktop matrix in ci.yml, so it uses the same path filter, setup, rust cache flavour (v1-rust-gpui, keyed by target and runner arch) and steps as the other lanes.
  • scripts/setup.js already picks the x86_64 native deps (FFmpeg framework) and ONNX Runtime from RUST_TARGET_TRIPLE, the same way the Intel release build does.
  • It runs the same tests as the arm64 lane, natively on Intel: cargo test --bin cap-gpui and cargo test -p cap-gpui-kernels. That also covers the Intel-only code paths behind cfg(all(target_os = "macos", target_arch = "x86_64")), which no test ran before.

Runner and duration:

  • macos-26-intel, the newest GitHub-hosted Intel image (macos-15-intel is the only other one). Blacksmith has no Intel Macs.
  • It has 4 vCPUs. With no cache the first run took about 65 minutes (54 minutes of that compiling), which fits under the existing 90 minute job timeout. The cache is only saved on main, so pull requests get warm runs once this has run on main.
  • First run: 1187 passed, 0 failed for cap-gpui (the arm64 lane runs 3 more tests that are compiled out on Intel macOS), and 31 passed for cap-gpui-kernels.

Engine verify on Intel is left out for now. It would need a new platform in scripts/verify/suites.json with its own case floors, and hosted Intel VMs have no usable GPU or hardware video decode, so it is better as an optional follow-up than a required check.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no blocking issues were found.

Summary

Adds native Intel macOS coverage to the existing GPUI desktop CI job.

  • GPUI desktop CI now tests Intel macOS on an Intel runner.

No actionable issues were found.

Reviews (2) · Last reviewed commit: "ci: build and test GPUI desktop on Intel..." · Reviewed by Greptile

@vercel

vercel Bot commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
cap-status Ready Ready Preview Oct 18, 2026 6:39pm UTC

@richiemcilroy

Copy link
Copy Markdown
Member Author

@greptileai review

@richiemcilroy
richiemcilroy marked this pull request as ready for review October 19, 2026 09:02

@capy-ai capy-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Capy found no issues.

Open in Capy

@richiemcilroy
richiemcilroy merged commit 053c121 into main Oct 19, 2026
53 checks passed

This branch was successfully deployed

2 active deployments
Preview – cap-web — b335f7cb Deployed Oct 18, 2026 by vercel[bot]
Preview – cap-status — b335f7cb Deployed Oct 18, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant