| 30 Apr 2025 |
 leona | To my knowledge thats not really possible / helpful because of the limitations of the hydra scheduler | 20:55:32 |
 Morgan (@numinit) | I have no horse in this race, but was just the notetaker and that reminded me 😀 | 20:55:41 |
| leona | (infra, correct me if i'm wrong) | 20:55:46 |
 Grimmauld (any/all) | current bottleneck is the staging-next of this cycle, which needs K's haskell patches and some darwin love? | 20:57:53 |
| leona | by the default procedure ZHF would start after this cycle's staging-next is merged. I'm not sure what it really needs, but at least it needs 2-3 more days time, if not more. ZHF can also start before, but then we get breaking changes in the ZHF after it started, so not ideal but acceptable | 21:00:01 |
 hexa | no scaling possible right now | 21:01:04 |
 Tristan Ross | In reply to @leona:leona.is
I'll publish a - hopefully good - announcement explaining the situation we're in, and start the ZHF from there. Otherwise time is too limited.. Cool, I'll try to help out with my 128 core system. Will be looking for the ZHF fixes label. | 21:34:50 |
| 1 May 2025 |
|  @bjsowa:matrix.org joined the room. | 00:04:56 |
| Morgan (@numinit) | Yeah I'll toss stuff at it for x86_64 on an EPYC, down to help stabilize | 06:02:25 |
| Morgan (@numinit) | Have both an EPYC 2 and EPYC 4 to toss at ZHF PRs this time :D | 06:03:37 |
| hexa | Darwin capacity is what hydra is missing | 12:56:48 |
| hexa | We have sufficient Linux capability | 12:57:07 |
| leona | ZHF started: https://github.com/NixOS/nixpkgs/issues/403336 | 15:11:58 |
