checks.x86_64-linux.status-up-to-date
- system
- x86_64-linux
- status
- cached
- started
- —
- finished
- 2026-11-12 10:08:41 UTC
- total
- —
- derivation
- /nix/store/p1y0n7y38zpb1s6layn7rgsz7v50l488-status-up-to-date.drv
- output
- /nix/store/qqw3gydfd5ix647srm5wz8s7c2pjbwbz-status-up-to-date
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/github/applicative-systems/dos/eval/176#status-up-to-date
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) | 213 ms | — |
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 |