Flaky CI Failure: Cache all Nix Outputs — codesign_allocate missing on macOS runner

[github-actions]

Flaky CI Failure: Cache all Nix Outputs — codesign_allocate missing on macOS runner

Workflow: Cache all Nix Outputs
Failed run: https://github.com/xmtp/libxmtp/actions/runs/30407408718
Commit: 534a417
Failed jobs: build (warp-macos-26-arm64-12x)

Summary

The Nix build for bindings-node-js-napi-aarch64-apple-darwin aborted during its fixupPhase when codesign failed to spawn codesign_allocate (No such file or directory). This caused an abort trap (exit code 134), which propagated as 13 cascading dependency failures and ultimately failed the entire nix build invocation. The failure is specific to the macOS ARM runner and the darwin stdenv code-signing step.

Error Details

bindings-node-js-napi-aarch64-apple-darwin> patching script interpreter paths in /nix/store/q4pd8lfs9gr9i8sq0mh71wbmbg4sz9xc-bindings-node-js-napi-aarch64-apple-darwin-1.11.0-dev
bindings-node-js-napi-aarch64-apple-darwin> libc++abi: terminating due to uncaught exception of type std::runtime_error: Failed to spawn codesign_allocate: No such file or directory
bindings-node-js-napi-aarch64-apple-darwin> /nix/store/7y0n5ycm25rx292np9gvvrwm3valcy8b-stdenv-darwin/setup: line 295: 41208 Abort trap: 6              codesign --force --sign - "$NODE_LIB"

error: Cannot build '/nix/store/5yc5plf334qpfq7mk85a7qsc88p8ck10-bindings-node-js-napi-aarch64-apple-darwin-1.11.0-dev.drv'.
       Reason: builder failed with exit code 134.

error: Cannot build '/nix/store/3lpm0fv82xkb3g70fnabj8h7sdhc4vms-xmtpv3-android-fast.drv'.
       Reason: 1 dependency failed.

error: Cannot build '/nix/store/phx1gbi2qkxhnjfqnjl8bzd3aqp24182-xmtpv3-android.drv'.
       Reason: 4 dependencies failed.

error: Cannot build '/nix/store/fphnfnm1sfimbn5snrhchb0nqyz89mqy-devour-output.json.drv'.
       Reason: 13 dependencies failed.

Error: `nix build` failed; exit code: Some(1)

Analysis

codesign on macOS uses codesign_allocate as a helper tool (typically located in the Xcode toolchain). The Nix darwin stdenv's fixupPhase runs codesign --force --sign - on the built .node library, but codesign_allocate could not be found on the runner PATH. This suggests the macOS Warp runner (warp-macos-26-arm64-12x) had a misconfigured or incomplete Xcode toolchain at the time of the run. This is an infrastructure failure (runner-side toolchain issue), not a test or code regression. Other targets built successfully on the same run (WASM, iOS xcframework, macOS darwin binary).

---

Reported by Flaky Failure Watcher

[github-actions]

Recurrence — 2026-07-29

Failed run: https://github.com/xmtp/libxmtp/actions/runs/30414469253
Commit: ddeab1f

Identical failure on a subsequent commit (~2 hours after the first occurrence). Same stdenv path, same abort trap (exit code 134), same 13 cascading dependency failures. The recurrence on a different commit confirms this is a persistent runner-side toolchain issue rather than a single transient glitch.

[github-actions]

Recurrence — 2026-07-29

Failed run: https://github.com/xmtp/libxmtp/actions/runs/30429460672
Commit: ddeab1f

This is the same codesign_allocate: No such file or directory failure but now occurring in the Release workflow (not just the Cache all Nix Outputs workflow). The failure blocked the release-node-sdk / bindings / build-macos (darwin-arm64) job, causing the downstream release-node-sdk / bindings / publish, release-node-sdk / build, and release-node-sdk / publish jobs to be skipped. The error signature is identical — same stdenv path, same derivation, same abort trap exit code 134 — but the impact is now broader, blocking the nightly release pipeline for the Node SDK.