| 10 Oct 2025 |
 uep | i know.. i've been running c9b6 since yesterday | 06:02:09 |
 vcunat | The channel scripts have extra code to avoid the possibility of channels going backwards - exactly for similar situations. | 06:02:50 |
| uep | so, i assumed hydra had been restarted and forgotten some of those jobs since clearly they had already run | 06:03:19 |
| uep | but explicit restarts makes sense too | 06:03:46 |
| vcunat | This doesn't happen automatically. | 06:04:06 |
| uep | * but explicit job restarts makes sense too | 06:04:10 |
| vcunat | But I don't know who did it. No audits for that. | 06:04:16 |
| uep | yeah, to be clear, i wasn't worried about the channel going backwards, what i meant about going backwards was just the build count progress. | 06:07:54 |
| uep | but if that's because (say) there are flaky python tests again and just rerunning lets more things land in cache, ok | 06:08:44 |
| vcunat | Hydra doesn't allow you to restart succeeded builds. | 06:09:09 |
| vcunat | So this is a relatively common situation for us. I was just trying to find out if there's something more anomalous, but it doesn't sound so. | 06:11:52 |
| uep | yeah, i thought it was hydra being flaky rather than deliberately retrying failed, possibly flaky, builds for evals that were already complete.. because it's been like this all week. | 06:13:31 |
| uep | never mind, thanks for the clarification | 06:13:48 |
| 11 Oct 2025 |
 hexa (signing key rotation when) | updating the m1 macs to 15.7.1 | 15:03:45 |
| hexa (signing key rotation when) | done | 15:19:12 |
| 13 Oct 2025 |
 teutat3s | Could someone restart the electron 38 hydra job in trunk-combined? It looks like various jobs failed, this one ran out of disk space
https://hydra.nixos.org/build/310015857/nixlog/1 | 15:59:16 |
| teutat3s | It was also reported here: https://github.com/NixOS/nixpkgs/issues/451482 | 16:00:16 |
|  vivekanandan_ks joined the room. | 18:57:46 |
| teutat3s | Seems to fail reliably 😄 I see this again:
fatal error: error in backend: IO failure on output stream: No space left on device
| 19:43:22 |
| teutat3s | * Thanks for restarting the build. It seems to fail reliably 😄 I see this again:
fatal error: error in backend: IO failure on output stream: No space left on device
| 19:43:54 |
| vcunat | What do you mean? The build succeded on Hydra now. | 19:49:54 |
| vcunat | * What do you mean? The build succeeded on Hydra now. | 19:50:00 |
| vcunat | https://hydra.nixos.org/build/310015857 | 19:50:07 |
| vcunat | "No space left on device" can be reliable if you still have similar (low) amount of space. | 19:50:46 |
| teutat3s | Nice, thanks. I must have looked at the wrong job, sorry for the noise.
How do you get to that build? | 19:51:55 |
| vcunat | Just deleted a suffix of your URL. | 19:52:40 |
| vcunat | * Just deleted a suffix of your URL 😉 | 19:52:56 |
| 14 Oct 2025 |
 Sami Liedes | Now that I've been running world rebuilds on my home workstation... does it ever happen in hydras that the builds get essentially serialized by something like binutils ./configure? Or is there always enough derivations to build that this doesn't happen? (I think it happens somewhat necessarily if rebuilding a single nixos, but if I was for example building nixos for 8 architectures on the same machine, I'm pretty sure I could saturate all cores.) | 17:10:41 |
 K900 | Yes | 17:11:34 |
| Sami Liedes | I looked into nix cgroups. What a mess. I have this hypothesis that this would happen much less if it used cgroups so that each builder (not each process of each builder) gets equal cpu. | 17:11:33 |
