13 Aug 2025 |
Mic92 | https://github.com/NixOS/hydra/pull/1506 Someone who would have time to test this? | 08:12:02 |
ElvishJerricco | ugh, I'm still getting the issue where the queue runner refuses to continue through the queue after any builds fail, even though the disabledUntil thing on my builder is in the past. | 08:17:48 |
sterni | appears not https://github.com/nix-community/nix-eval-jobs/blob/a579b1a416dc04d50c0dc2832e9da24b0d08dbac/src/worker.cc#L261-L280 | 11:29:54 |
John Ericson | Simon Hauser: I was talking to Mic92 just now. I am hoping that the new queue runner can (a) go in the repo, (b) be integrated into hydra's test suite | 20:22:25 |
John Ericson | otherwise, the test suite will no longer match the reality of what is deployed | 20:22:39 |
14 Aug 2025 |
Simon Hauser | That was the plan, I'll work on it this weekend | 16:21:48 |
18 Aug 2025 |
| knownasred set a profile picture. | 14:26:00 |
| knownasred changed their display name from redblueflame to knownasred. | 14:26:05 |
| @sjanssen:matrix.org left the room. | 21:50:04 |
20 Aug 2025 |
| dgrig joined the room. | 17:43:06 |
21 Aug 2025 |
hacker1024 | Was there documentation on defining aggregate jobs somewhere? I swear I read something at one point, but I can't find anything in the manual now... | 01:31:48 |
| @creepinson:matrix.org joined the room. | 22:11:27 |
22 Aug 2025 |
| elikoga changed their profile picture. | 17:28:12 |
23 Aug 2025 |
Janne | None I know about | 17:38:18 |
shawn8901 | Not sure if that helps, but here is the code for the aggregate https://github.com/NixOS/nixpkgs/blob/76d197f4b03c0ad103b0254d6c333fca427133ba/pkgs/build-support/release/default.nix#L122
I am then doing something like that on my flake to define an overall hydraJob for all my nixosConfigurations
${name} = nixpkgs.legacyPackages.x86_64-linux.releaseTools.aggregate {
inherit name;
meta = {
schedulingPriority = 10;
};
constituents = map (n: "nixos." + n) (nixpkgs.lib.attrNames self.nixosConfigurations);
};
| 22:18:05 |
24 Aug 2025 |
Janne | Oh man, I hope the parsing code is sane. Because I haven't looked at that when I fixed the other XSS thingies | 17:46:16 |
26 Aug 2025 |
ElvishJerricco | is there a way to get the eval errors from an evaluation as a JSON array of the error messages? e.g. https://hydra.nixos.org/eval/1817978#tabs-errors | 05:02:42 |
ElvishJerricco | I'm basically just trying to get the errors so I can filter out the ones I know have nothing to do with me :P | 05:03:00 |
Janne | lol, no | 08:10:08 |
Janne | that would be useful | 08:10:17 |
Janne | iirc, we get the eval errors from the stderr (or stdout) of nix-eval-jobs and that's simply a long string | 08:10:36 |
27 Aug 2025 |
| connor (he/him) (UTC-7) changed their display name from connor (he/him) (UTC-7) to connor (he/him) (UTC+1). | 18:33:46 |
28 Aug 2025 |
hacker1024 | I want to prepend the jobset name to this GitLab status API call, but the Builds table only has a column for the jobset ID. I'm not too familiar with Perl or SQL - is there an easy way to look up the appropriate name from the Jobsets table here?
Or is the jobset name available through some other API?
| 06:36:50 |
hacker1024 | Got it - $build->jobset->get_column('name') | 07:12:05 |
| @lgcl:lgcl.de left the room. | 08:32:42 |
29 Aug 2025 |
| @luna-null:matrix.org left the room. | 02:40:36 |
| magic_rb changed their profile picture. | 19:29:39 |
31 Aug 2025 |
| teutat3s joined the room. | 16:44:40 |
teutat3s | Is there any workaround to fix a cached failure on hydra that cannot be reproduced locally? Or is the solution to just wait until some cache expiry?
Asking for https://hydra.nixos.org/build/306350994 | 16:47:29 |
K900 | Restarted | 17:05:05 |