packages.x86_64-linux.personal-website
- system
- x86_64-linux
- status
- success
- started
- 2026-09-09 16:39:04 UTC
- finished
- 2026-09-09 16:39:54 UTC
- total
- 49s
- derivation
- /nix/store/7g1qrsp69f217kwy3v2vk590z6160a52-personal-website-2.12.5.drv
- output
- /nix/store/0iaa5yrzxfgkqmrnn3iwb55572dlf4x8-personal-website-2.12.5
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.snyssen.be/flake/github/snyssen/personal-website/eval/304#personal-website
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) | 729 ms | 398.12 KB |
| build (net, on builder) | 48s | — |
| pull (output closure ← builder) | 362 ms | 320.53 KB |
| publish (coord → binary cache) | 1m 15s | — |
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 | success | pushed output closure to s3://cache?endpoint=https://s3.snyssen.be®ion=home |