27 May 2024 |
stigo | ... which I can see that you're actually doing :) woops | 12:58:23 |
stigo | In reply to @hexa:lossy.network and you can trigger evals when you're ready that would be useful, so I don't have to annoy staging until the update is in a good state | 12:58:57 |
hexa | do you have a specific entrypoint? | 12:59:29 |
hexa | see pkgs/top-level/release-*.nix | 13:00:14 |
hexa | the simplest would be release-r.nix | 13:00:56 |
stigo | ah, TIL about entrypoints. should prob create one for perl then that maps trough all perlPackages based on release-r.nix ? | 13:02:37 |
hexa | and maybe you'll also want a an aggreate tested job? | 13:02:59 |
stigo | not sure what that means, but sounds good :P | 13:03:20 |
hexa | haha 😄 | 13:03:27 |
hexa | like the tested jobset on trunk-combined and unstable-small | 13:03:40 |
hexa | but it doesn't matter so much, since there is no channel created from it | 13:03:49 |
hexa | but it would allow you to track packages outside of perlPackages, that you think are important and depend on the perl infra | 13:04:17 |
stigo | hydra-unstable is one package that I use to smoke test | 13:04:45 |
hexa | cool! | 13:04:56 |
stigo | also, usually test some cross builds that have been problematic, that would make sense to have in a tested jobset | 13:05:41 |
stigo | usually most failures show up in the unit tests in respective perlPackages though | 13:06:29 |
@qbit:tapenet.org | In reply to @stigo:matrix.org I usually just use let perl' = perl.withPackages(...); and put that in buildInputs ah, ok | 13:09:09 |
@qbit:tapenet.org | ty | 13:09:15 |
hexa | https://hydra.nixos.org/jobset/nixpkgs/perl-updates | 13:20:41 |
stigo | connected to the perl-updates branch, right? | 13:21:49 |
vcunat | Possibly with slightly lower shares, as this value is close to trunk-combined . | 13:22:00 |
vcunat | In reply to @stigo:matrix.org connected to the perl-updates branch, right? Yes. You can see where it fetches from in https://hydra.nixos.org/jobset/nixpkgs/perl-updates#tabs-configuration | 13:22:32 |