-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
Eval check not catching certain eval errors #397184
Copy link
Copy link
Open
Labels
2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.mdhttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: continuous integrationAffects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub ActionsAffects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions
Metadata
Metadata
Assignees
Labels
2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.mdhttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: continuous integrationAffects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub ActionsAffects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions
Fields
Give feedbackNo fields configured for issues without a type.
See #396749 (comment).
To reproduce on master:
$ nix-env -f pkgs/top-level/release-attrpaths-parallel.nix --eval-system aarch64-linux --option restrict-eval true --option allow-import-from-derivation false --query --available --no-name --attr-path --out-path --show-trace --arg chunkSize "1" --arg myChunk 0 --arg attrpathFile ./doesntmatter.json --arg systems "[\"aarch64-linux\"]" --arg checkMeta true --arg includeBroken true -I . -I ./doesntmatter.jsonIf you
nix-instantiate --evalrelease-attrpaths-parallel.nix, this issue does get caught, which I guess begs the question: is this intentional? What kinds of eval errors is this supposed to catch, then? Should we fix it?cc @infinisil @philiptaron @wolfgangwalther