After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build a08b3a4d19.tar.gz \
--argstr baseRev b32a094368
result/bin/apply-formatting $NIXPKGS_PATH
This reverts commit c7aef6dedb.
I believe it should work again since today, though I'm being a bit
conservative, pushing to `staging-next` instead of `master`.
It was failing because the pager wasn't set, causing the message
error: executing '': No such file or directory
to pollute the JSON output.
https://hydra.nixos.org/build/154768851
Issue #76776.
The build hasn't worked for months (even on 20.09). Now also my
dedicated machine broke, and I don't feel like maintaining it until
the job has any chance of succeeding.
(I don't know why exactly it's failing.)
These have a hug log that will hit “log limit exceeded” on Hydra. This
commit skips the biggest offenders - qaDrv and qaDrvAggresive, giving
smaller logs.
https://hydra.nixos.org/build/94487387
From these three values, I believe it's most meaningful to track
one of the higher ones and their difference (qaCountBroken).
It's a bit unclear which of the higher ones - I have no data on that,
so I kept the one used before the parent commit.
Before ae16dd1a15 `nix-env.qaCount` and
`nix-env.qaCountDrv` were equivalent, after that change that is no longer
the case so this needs a separate metric now.