We are seeing an intermittent CI failure on Namespace-managed GitHub Actions runners (macOS arm64) where Nix evaluation fails because the runner's /nix/store appears internally inconsistent (store DB references paths that don't exist).
This is not a flaky unit/integration test: the failure happens before our actual tests run.
- Job:
test (namespace-profile-macos-arm64) - Fails during Nix/devenv evaluation (before
viteststarts) - Error signature (key line):
error: path '/nix/store/...-make-symlinks-relative.sh' is not valid
The error is emitted while evaluating bootstrap-stage0-stdenv-darwin (Darwin stdenv bootstrap), which suggests missing store paths.
We also see downstream/secondary errors like:
Failed to convert config.cachix to JSONEvaluation error: Failed to get attribute 'package'while evaluatingcachix.package
Those look like consequences of the earlier invalid store path.
Example failing runs in a public repo:
- 2026-02-12: https://github.com/overengineeringstudio/effect-utils/actions/runs/21937239839
- failing job:
test (namespace-profile-macos-arm64)
- failing job:
- 2026-02-09: https://github.com/overengineeringstudio/effect-utils/actions/runs/21840384378
- failing job:
test (namespace-profile-macos-arm64)
- failing job:
Internal tracking issue (what we collect when it happens again):
Upstream issue filed for Namespace:
In the failing run logs (linked above), GitHub Actions prints Namespace runner details:
- OS: macOS
- Architecture: arm64
- A "User Bundled Cache" is enabled
We suspect this may involve persisted runner state / bundled cache restoring a broken Nix store state.
Questions for Namespace maintainers / runners team:
- Are there known issues on macOS Namespace runners where
/nix/storecan become inconsistent (missing paths)? - Is there a supported way to force a clean Nix store (or disable store persistence) for a runner profile?
- If the bundled cache can become corrupted, is there a supported mechanism to invalidate/reset it automatically?
- This is flaky and we do not have a reliable reproduction.
- We are improving CI logging so that future failures include more actionable Nix store verification output.