| 26 Jun 2026 |
 emily | because it depends on how Hydra sets up the Nixpkgs checkout etc | 14:55:10 |
 Mic92 | In reply to @emilazy:matrix.org
it would be very sad to give up on Nix/Hydra as the integrated build system for all of NixOS imo From a security perspective I would be better to not run so much code on there. It has way too many scary legacy features | 14:59:54 |
| Mic92 | * From a security perspective it would be better to not run so much code on there. It has way too many scary legacy features | 15:00:05 |
| Mic92 | There a more than enough general purpose CIs for these tasks. I don't see why we need something special here | 15:02:16 |
| emily | I'm not sure what you mean. every package is built on Hydra so Hydra security problems are game over regardless | 15:06:07 |
| emily | or do you just mean "channel scripts code running directly on the Hydra node?" | 15:06:16 |
 K900 | Channel scripts aren't on the Hydra node though? | 15:06:58 |
| emily | I didn't know where they run tbh | 15:07:09 |
| emily | but I'm not sure how adding another build to the jobset to replace some code running outside the sandbox would be a security regression | 15:07:27 |
 hexa | they run on pluto.nixos.org | 15:08:16 |
| hexa | the host that runs monitoring, too | 15:08:21 |
| hexa | not on any system that has anything else to do with the hydra stack | 15:08:40 |
| emily | right. well I am concerned about Hydra security in general but as long as stdenv gets built on there we can't really improve our security by moving things out of Hydra builds | 15:09:26 |
|  jutty joined the room. | 19:46:05 |
|  Sapphire joined the room. | 21:16:26 |
 John Ericson | Hoping we can rip out a lot of abandoned stuff | 21:34:31 |
| John Ericson | I do like drv-level scheduling, that's the core value proposition of hydra | 21:34:59 |
| hexa | it's where most other scheduling systems fail | 21:40:11 |
| 27 Jun 2026 |
 Yorusaka Miyabi | https://hydra.nixos.org/build/332738696/download/1/manual/ Yields a 500 error | 03:35:18 |
| Yorusaka Miyabi | (Build refers to develop version of Nix manual) | 03:35:43 |
 Grimmauld (any/all) | i just had some fun plotting occupancy against 1d standard deviation (blue). It seems with new queue runner, we have much more fluctuations in occupancy. Why is this? Intuitively i would expect more deviation with worse scheduling. Don't get me wrong, total utilization seems to be higher, but this looks like we may have a delay between a job being finished and a new one being queued, causing occupation to temporarily drop | 05:24:05 |
| Grimmauld (any/all) | 
Download image.png | 05:24:05 |
| Mic92 | Before we don't have https://github.com/NixOS/infra/pull/1099 I don't think those graphs are very meaningful. There are some known bottlenecks I introduced to make it stable. | 05:42:58 |
| Mic92 | hexa (signing key rotation when): I also added now also the patch to macOS builders: https://github.com/NixOS/infra/pull/1104 But my internet upload is still not great until Sunday, if you wanted to take a stab if it. | 05:52:11 |
| Mic92 | * hexa (signing key rotation when): I also added now also the patch to macOS builders: https://github.com/NixOS/infra/pull/1104 But my internet upload is still not great until Sunday, if you wanted to take a stab earlier | 05:52:17 |
| Mic92 | * hexa (signing key rotation when): I also added now also the patch to macOS builders: https://github.com/NixOS/infra/pull/1104 But my internet upload is still not great until Sunday, if you wanted to take a stab at it earlier | 05:52:30 |
 whispers [& it/fae] | out of curiosity, is it expected/known that no *-linux jobs are being scheduled at all? the only one is https://hydra.nixos.org/build/332926387, which has been running for five hours. the rest of the machines seem to be sitting fully idle: https://hydra.nixos.org/machines | 06:05:06 |
| whispers [& it/fae] | * | 06:05:29 |
| whispers [& it/fae] | * | 06:06:48 |
| whispers [& it/fae] | * | 06:09:43 |
