| 2 Aug 2021 |
 Vladimír Čunát | (even though that bug was resolved quite quickly afterwards) | 20:29:19 |
| Vladimír Čunát | * Wendy was removed for a time. Then there was a bug resulting we had no big-parallel machine in the farm (for x86_64-linux), so as a quick fixup in the meantime wendy was brought back... and so far it's stayed :-) | 20:35:15 |
 Sandro | that means we can remove it again? | 20:46:47 |
| Vladimír Čunát | AFAIK it can be removed, as we do have others with the required features, but it maybe provides a noticeable part of the overall power. | 21:22:06 |
| 3 Aug 2021 |
|  Reventlov joined the room. | 07:18:55 |
| Sandro | how long do we wait extra when chromium lands on wendy again? half a day? | 08:30:24 |
| Vladimír Čunát | Those latest builds on wendy were taking roughly one day. (though it surely depends on circumstances) The "wait extra" might only really apply when Hydra is relatively idle. | 08:52:34 |
| Sandro | I meant this more like how much longer it takes to build chromium on wendy compared to some of the newer servers | 08:53:09 |
| Vladimír Čunát | I understood but I don't know. | 08:58:47 |
| Sandro | hmmm... 🤔 | 08:59:31 |
 lukegb (he/him) | I think the packet builders can build Chromium in just over 7h | 09:08:00 |
 nf | i found builds that took only 2h https://hydra.nixos.org/build/148765583#tabs-buildsteps | 09:36:12 |
| nf | not sure if these are actually building the same thing? | 09:36:26 |
| lukegb (he/him) | Yeah, that seems reasonable | 09:44:52 |
| Vladimír Čunát | ungoogled-chromium isn't exactly the same thing, but I expect that requirements on build time will be very similar. | 09:45:48 |
| nf | it's the chromium-unwrapped step that took 2h anyway | 10:14:59 |
| Vladimír Čunát | Both variants (normal and ungoogled) have separate -unwrapped builds. | 10:44:58 |
| nf | ok | 10:50:13 |
| 4 Aug 2021 |
 sterni | why is this job consistently failing? https://hydra.nixos.org/job/nixpkgs/cross-trunk/avr.buildPackages.gcc.x86_64-linux | 15:12:21 |
| sterni | it's a bit unfortunate that we don't have binary cache for avr-gcc, since it does build successfully when you try locally | 15:12:45 |
| sterni | are there some hydra settings to allow it more log maybe? | 15:13:25 |
| Vladimír Čunát | It would seem best to patch it in some way that reduces the huge amount of logs. | 15:35:09 |
| sterni | do dependency logs count towards that if they aren't scheduled separately? | 15:36:12 |
| sterni | I'm a bit confused why gcc would all of a sudden have a lot more logs for the avr target | 15:36:34 |
| sterni | the failure began when avr gcc was upgraded from 9 to 10 though | 15:37:02 |
| Vladimír Čunát | 64 MiB limit sounds high enough to me. | 15:41:01 |
| Vladimír Čunát | * 64 MiB limit sounds high enough to me. (even though logs will typically compress a lot) | 15:41:38 |
| 5 Aug 2021 |
 @grahamc:nixos.org | I think I wouldn't mind increasing the log limit | 14:16:22 |
| @grahamc:nixos.org | 64MiB is a lot though :) | 14:17:07 |
| @grahamc:nixos.org | either here: https://github.com/NixOS/hydra/blob/4e9455160270b9b933582501a47430690d66e5b4/src/hydra-queue-runner/hydra-queue-runner.cc#L45 or as a configuration setting in the nixos-org-configurations repo | 14:18:29 |
