ci: use nix-fast-build to speedup checks #156

Merged

jalil merged 1 commit from push-vrtqokrqvkvk into main

2025-03-16 19:29:07 +01:00

jalil commented

2025-03-16 19:26:27 +01:00

Owner

Should be a noticeable improvement c:

jalil self-assigned this 2025-03-16 19:26:27 +01:00

jalil added 1 commit 2025-03-16 19:26:27 +01:00

ci: use nix-fast-build to speedup checks

/ check-renovaterc (push) Successful in 3s

Details

/ build (push) Successful in 3s

Details

/ test (push) Waiting to run

Details

/ report-size (push) Waiting to run

Details

a4d3bc7c0c

Should be a noticeable improvement c:

jalil force-pushed push-vrtqokrqvkvk from a4d3bc7c0c to 08ea3271c1

2025-03-16 19:27:13 +01:00

Compare

forgejo-actions commented

2025-03-16 19:27:40 +01:00

First-time contributor

Flake output sizes

Definitions

Name: the name of the package/configuration.
Size: the closure size (size on disk/NAR size + all transitive dependencies).
NAR Size: the size of the build output (package without the dependencies).
[NAR] Size Change: the amount changed compared to the main branch.

Tips on reading this data

For NixOS configurations you generally care only about the Size (closure size/size on disk).
- Reduce the Size by disabling unneeded services/default packages.
For Packages you care about both the Size and the NAR Size.
- Reduce the NAR Size by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc.
- Reduce the Size by reducing the dependencies (e.g. buildInputs).
- Don't worry too much about size, some dependencies are deduplicated, e.g. glibc adds ~40MiB to the Size, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. musl is not gonna improve things.

Packages

Name	Size	Size Change	NAR Size	NAR Size Change
`default`	35MiB	0B	2.9MiB	0B
`git-cliff`	60MiB	0B	19MiB	0B
`webnsupdate`	35MiB	0B	2.9MiB	0B

## Flake output sizes <details><summary><b>Definitions</b></summary> - `Name`: the name of the package/configuration. - `Size`: the closure size (size on disk/NAR size + all transitive dependencies). - `NAR Size`: the size of the build output (package without the dependencies). - `[NAR] Size Change`: the amount changed compared to the main branch. </details> <details><summary><b>Tips on reading this data</b></summary> - For NixOS configurations you generally care only about the `Size` (closure size/size on disk). - Reduce the `Size` by disabling unneeded services/default packages. - For Packages you care about both the `Size` and the `NAR Size`. - Reduce the `NAR Size` by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc. - Reduce the `Size` by reducing the dependencies (e.g. `buildInputs`). - Don't worry too much about size, some dependencies are deduplicated, e.g. `glibc` adds ~40MiB to the `Size`, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. `musl` is not gonna improve things. </details> ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `default` | 35MiB | 0B | 2.9MiB | 0B | | `git-cliff` | 60MiB | 0B | 19MiB | 0B | | `webnsupdate` | 35MiB | 0B | 2.9MiB | 0B |

jalil merged commit 08ea3271c1 into main

2025-03-16 19:29:07 +01:00

jalil deleted branch push-vrtqokrqvkvk

2025-03-16 19:29:07 +01:00