packages.x86_64-linux.modules-markdown
- system
- x86_64-linux
- status
- success
- started
- 2026-11-11 12:49:36 UTC
- finished
- 2026-11-11 12:49:45 UTC
- total
- 8s
- derivation
- /nix/store/gkc9fm5kawng7c7wnp2xhfvcscbnlixx-options.md.drv
- output
- /nix/store/649gb00q175c6p6idxwmzgflzdvhc7nf-options.md
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/github/applicative-systems/dos/eval/172#modules-markdown
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) | 1s | 87.15 KB |
| build (net, on builder) | 5s | — |
| pull (output closure ← builder) | 978 ms | 23.22 KB |
| publish (coord → binary cache) | 272 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 |