checks.aarch64-linux.example-standalone
- system
- aarch64-linux
- status
- cached
- started
- —
- finished
- 2026-07-28 14:17:41 UTC
- total
- —
- derivation
- /nix/store/jg2nj0wmwypvxsg8r49rincgdz4sg5zb-pprintpp-example-project.drv
- output
- /nix/store/cqjasjizblv4iz81xxadxp24ffskv7qv-pprintpp-example-project
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/github/tfc/pprintpp/eval/109#example-standalone
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) | 1m 24s | — |
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://test-cache?endpoint=nbg1.your-objectstorage.com®ion=nbg1&addressing-style=virtual | success | pushed output closure to s3://test-cache?endpoint=nbg1.your-objectstorage.com®ion=nbg1&addressing-style=virtual |