checks.aarch64-linux.clippy
- system
- aarch64-linux
- status
- success
- started
- 2026-06-14 07:38:19 UTC
- finished
- 2026-06-14 07:40:20 UTC
- total
- 2m 0s
- derivation
- /nix/store/0isfz47d1bcvzc0sgz0jzf2gm103hjdh-gcan-1.0.0.drv
- output
- /nix/store/pf71c52vllpd3gypqvgxwg9ikffqgrxi-gcan-1.0.0
Run from cache
nix run --extra-experimental-features fetch-closure --accept-flake-config https://argunix.nix-consulting.net/flake/github/applicative-systems/gcan/eval/86#clippy
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) | 375 ms | 1.70 MB |
| build (net, on builder) | 1m 59s | — |
| pull (output closure ← builder) | 102 ms | 1.15 KB |
| publish (coord → binary cache) | 200 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 |