Closed shadowrylander closed 2 years ago
Sorry; just understood the error. What measures does Hydra take to handle failing packages, or where can I find them? This, for example, gets killed:
filterAttrs (n: v: all (b: b == true) [
(! elem n [ "prometheus-dmarc-exporter" ])
(tryEval v).success
((isDerivation v) && (v ? meta) && (v.meta ? broken))
]) legacyPackages
Most likely this will also use a ton of memory. flattenTree probably shouldn't be used like that :sweat_smile:
Aww... 😹 Ah, well; I guess I could just use legacyPAckages
. Could you tell me the difference between it and packages
, actually?
The only difference is when using nix flake check
, it will complain if packages
isn't a flat attrset of packages only. legacyPackages
allows any types of values. When you use commands like nix run
it will look into both, and prioritize packages
over legacyPackages
.
Ah; makes sense. Thanks for the clarification!
Describe the bug
flattenTree
cannot seem to flattenlegacyPackages
to apackages
-compatible format; the resulting attribute set is empty.To Reproduce
Steps to reproduce the behavior:
The commented
packages
assignments all fail, while the last one succeeds, verified bytrace packages
.Expected behavior
I thought the commented assignments result in the same attribute sets as the last assignment.
System information
NixOS 22.05
, usingnix (Nix) 2.5.0pre20211206_d1aaa7e
and the master branchflake-utils
.Additional context
Here is the actual config, as opposed to the minimal example above.