| 20 Sep 2024 |
 hacker1024 | Thanks for that! I got stuck there and gave up lol | 11:18:12 |
| hacker1024 | Now the only thing keeping me from upgrading is the fact that remote builds seem to have completely broke with Nix 2.21 | 11:18:47 |
 Mic92 | hacker1024: has it something to do with parsing keys? | 11:19:53 |
| hacker1024 | I don't think so, I'm getting the error that this person got
https://60228.dev/@leo/112413449703903627 | 11:20:20 |
| hacker1024 | Related: https://github.com/NixOS/nix/issues/9961#issuecomment-1949315154
But I tried using the same Nix version as Hydra on my remote builders and that didn't help | 11:20:53 |
 cleverca22 | for my hydra, remote building still works, its local building thats broken | 11:21:45 |
| hacker1024 | * Related: https://github.com/NixOS/nix/issues/9961
But I tried using the same Nix version as Hydra on my remote builders and that didn't help | 11:21:46 |
| cleverca22 | { hostName = "localhost"; mandatoryFeatures = [ "local" ]; systems = [ "x86_64-linux" "i686-linux" ]; maxJobs = 4; } | 11:22:07 |
| Mic92 | thans | 11:22:19 |
| hacker1024 | In reply to @cleverca22:matrix.org
for my hydra, remote building still works, its local building thats broken I read something somewhere about localhost no longer being a valid store URI | 11:22:17 |
| hacker1024 | I can't remember where or what the solution was | 11:22:23 |
| cleverca22 | i had this in the build machines, it was an old trick to allow hydra to execute certain jobs locally | 11:22:24 |
| Mic92 | * thanks. | 11:22:25 |
| cleverca22 | but now it just fails with an ssh error | 11:22:31 |
| cleverca22 | Mic92: binary cache action now works, when running my hydra from the commit in my PR:
[0/103 built, 16/126/310 copied (169.4/2690.9 MiB), 45.6/364.7 MiB DL] fetching patch-2.7.6 from https://hydra.angeldsis.com | 11:26:59 |
 John Ericson | In reply to @joerg:thalheim.io
John Ericson: can you explain how these branches in hydra are supposed to be used? The nix- ones are supposed to be the latest commit with that version of Nix | 20:37:39 |
| 21 Sep 2024 |
|  @luna-null:matrix.org joined the room. | 05:45:40 |
 sterni (he/him) | does hydra display anywhere if a job failed due to disallowedReferences or similar? | 10:41:45 |
| 23 Sep 2024 |
|  elikoga joined the room. | 15:30:42 |
|  connor (burnt/out) (UTC-8) changed their display name from connor (he/him) (UTC-5) to connor (he/him) (UTC-7). | 17:57:43 |
| 24 Sep 2024 |
|  @asymmetric:matrix.dapp.org.uk joined the room. | 14:42:55 |
| @asymmetric:matrix.dapp.org.uk | is there a way to subscribe to hydra build failures for a specific package?
if not, is there a stable way to go attr_path -> build log? as in: i am interested in fetching the latest x86_64 build of package foo in the jobset nixos:release-24.05, is there a stable url i can periodically check for that?
| 14:47:57 |
| @asymmetric:matrix.dapp.org.uk | ah i guess this would answer my 2nd question: https://hydra.nixos.org/job/nixpkgs/staging-next-24.05/rippled.x86_64-linux | 15:14:09 |
| @asymmetric:matrix.dapp.org.uk | why is the job (chosen at random) not present in the nixos/release-24.05 jobset? https://hydra.nixos.org/job/nixos/release-24.05/rippled.x86_64-linux | 15:15:34 |
| @asymmetric:matrix.dapp.org.uk | i'm not sure i understand the text on the page: was it removed by hand? or if it had an error, why isn't the error shown? | 15:16:08 |
 K900 | https://hydra.nixos.org/job/nixos/release-24.05/nixpkgs.rippled.x86_64-linux | 15:17:59 |
| K900 | Wrong job name | 15:18:01 |
| K900 | The nixpkgs jobsets only build packages, nixos jobsets build packages and nixos tests, so packages get an extra nixpkgs. namespace | 15:18:19 |
|  Nikolay Kolev changed their profile picture. | 22:27:29 |
|  mei 🌒& changed their profile picture. | 23:20:39 |
