| 3 Aug 2021 |
 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 |
| Vladimír Čunát | It would make sense to me to allow increasing it in relatively important derivations where we see no easy way of reducing the logs. That way the overall cost increase should be negligible. | 15:17:47 |
| Vladimír Čunát | * It would make sense to me to allow increasing it just in relatively important derivations where we see no easy way of reducing the logs. That way the overall cost increase should be negligible. | 15:17:58 |
| Vladimír Čunát | * It would make sense to me to allow increasing it just in relatively important derivations where we see no easy way of reducing the logs. (e.g. like we have for the timeouts) That way the overall cost increase should be negligible. | 15:18:16 |
| sterni | tbh I half expected there to be a meta setting for it already :) | 15:53:04 |
| 9 Aug 2021 |
 hexa | https://github.com/NixOS/nixpkgs/pull/133289 | 20:53:51 |
| hexa | author asks for someone with hydra knowledge to check their assumptions | 20:54:06 |
| 12 Aug 2021 |
| hexa | I have no particular love for wendy, but ongoing SIGILL on packages that are costly to build yourself (pytorch, tensorflow, numpy) are less than ideal | 11:25:21 |
| hexa | https://hydra.nixos.org/build/149565546 | 11:25:30 |
