nixosConfigurations.purplehaze
- system
- x86_64-linux
- status
- cached
- started
- —
- finished
- 2026-09-14 15:22:49 UTC
- total
- —
- derivation
- /nix/store/pd5wmnjjdkyqqnh01fmwfbfvmg70l312-nixos-system-purplehaze-26.05.20260910.d58a46e.drv
- output
- /nix/store/gvlbvi0snaav6kdl2l80n70110mrrmvd-nixos-system-purplehaze-26.05.20260910.d58a46e
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.snyssen.be/flake/github/snyssen/mother-of-all-infra/eval/342#purplehaze
Requires this argunix's cache in
trusted-substituters +
trusted-public-keys — see
/cache for
the one-time setup snippet.
transport & build
Time and data spent uploading the build inputs to the builder, running the build, and downloading the outputs back. Bytes are measured between argunix and the builder; the build duration is the build itself, not including transfer.
| phase | duration | bytes |
|---|---|---|
| push (drv closure → builder) | — | — |
| build (net, on builder) | — | — |
| pull (output closure ← builder) | — | — |
| publish (coord → binary cache) | 5m 0s | — |
registry & effects
What argunix did with this build's output after it was realised — pushing the image to a registry, attaching its SBOM. The detail line of a registry push is the reference you pull.
| effect | status | detail |
|---|---|---|
| cache-push · s3://cache?endpoint=https://s3.snyssen.be®ion=home | failure | `nix copy --to s3://cache?endpoint=https://s3.snyssen.be®ion=home` timed out after 300s |