Exact

Exact Union RegExp

Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Transaction Science 7ef7191950 CI: two macOS legs depended on runner state the pin change cleared or never had ... Both failed on this branch for reasons that are about how the `macos` label is provisioned, not about the code. That label is served by four hosts, which are not identically set up: tx-dev-mac Mac Studio M3 Ultra full Xcode tx-mbp-m5max-48 MacBook Pro M5 Max 48 full Xcode tx-mbp-m4max-128 MacBook Pro M4 Max 128 full Xcode tx-imac-pro-macos iMac Pro (x86_64) Command Line Tools only Which host takes a job is not predictable, so a leg that needs more than the base install passes or fails by where it lands. wai-examples, the apple-app step `rustup target add` had never named the apple slices' targets; the job ran on targets some earlier toolchain happened to have left on the runner. A target's std belongs to one toolchain, so moving the pin to 1.99.1 left the job with none of them and the macos slice failed at x86_64-apple-darwin with E0463, "can't find crate for `core`". The five targets are now added by name, the same set and the same line as wai-sink-swift.yml, which has always done this. The tvos slices' nightly is a separate toolchain and keeps its own targets, so it is not re-added. jouleclaw-fabrics, the Metal shader step Xcode ships the Metal compiler as a downloadable component, and an Xcode or macOS upgrade uninstalls it. Three of the four hosts reported `Status: uninstalled` (Xcode 27B47), and on those every `xcrun metal` fails with "missing Metal Toolchain" -- which check-metal-shaders.py reports as all 44 shaders failing to compile, so a provisioning gap reads as a code failure. The job now installs the component if it is absent. It is idempotent and persists on the host, so the download happens once per host per Xcode version, and it makes the job correct wherever it lands instead of only on the host that was provisioned by hand. Where there is no full Xcode -- the iMac Pro -- it now fails with that as the stated reason rather than as 44 broken shaders. Verified on two real hosts rather than reasoned about: the absent branch takes the download path on a host reporting `uninstalled`, and the present branch short-circuits on the Studio, printing `Apple metal version 32023.922`. The component was installed on the Studio by hand first and `scripts/check-metal-shaders.py` then reported 44 compiled, 0 failed, 0 skipped, which is what confirmed the shaders themselves are fine. Neither leg's workflow had said what it needed; both read it off a host. That is the class of fault a toolchain change exposes, because it clears per-toolchain state while leaving the host otherwise untouched. Co-Authored-By: Claude Opus 5 <[email protected]>		2026-11-03 00:45:20 -05:00
..
workflows	CI: two macOS legs depended on runner state the pin change cleared or never had	2026-11-03 00:45:20 -05:00