| 17 Jan 2026 |
 Arian | I get:
aggregate job 'tested' references non-existent job 'nixos.channel'
aggregate job 'tested' references non-existent job 'nixpkgs.tarball'
aggregate job 'tested' references non-existent job 'nixpkgs.release-checks'
aggregate job 'tested' references non-existent job 'nixos.tests.installer.lvm.x86_64-linux'
aggregate job 'tested' references non-existent job 'nixos.tests.installer.separateBoot.x86_64-linux'
aggregate job 'tested' references non-existent job 'nixos.tests.installer.simple.x86_64-linux'
aggregate job 'tested' references non-existent job 'nixos.dummy.aarch64-linux'
aggregate job 'tested' references non-existent job 'nixos.dummy.x86_64-linux'
aggregate job 'tested' references non-existent job 'nixos.manual.aarch64-linux'
aggregate job 'tested' references non-existent job 'nixos.manual.x86_64-linux'
aggregate job 'tested' references non-existent job 'nixos.tests.acme.http01-builtin.aarch64-linux'
aggregate job 'tested' references non-existent job 'nixos.tests.acme.http01-builtin.x86_64-linux'
| 22:06:54 |
| Arian | Oh apparently when we moved hydra to nix-eval-jobs we just pass --force-recurse ? Is all this recurseForDerivations annotations that we carefully put in all the hydra jobs in release.nix completely superfluous these days? Can all that code die now? | 22:15:51 |
 vcunat | That's on nixpkgs side to distinguish where to recurse and where not to. | 22:18:17 |
| vcunat | (recursing everywhere would've been easy even in the past, I believe) | 22:18:30 |
| vcunat | For example right now on master we have a full python312Packages set, but we don't want Hydra to build (or eval) it all. | 22:20:15 |
| Arian | Ah I see! | 22:25:52 |
