| 17 Mar 2024 |
|  cblacktech joined the room. | 17:08:46 |
| 18 Mar 2024 |
|  darkwater4213 joined the room. | 00:40:09 |
| 19 Mar 2024 |
|  mjolnirchanged room power levels. | 00:29:57 |
 ElvishJerricco | How do I fix a Output limit exceeded error? Restarting builds doesn't fix it. I know the issue occurred while compressing a successful derivation before uploading it to the binary cache. | 17:06:23 |
 K900 | That means the output exceeds the size limit | 17:07:06 |
| ElvishJerricco | K900 ⚡️: .... there's a size limit? | 17:07:25 |
| ElvishJerricco | how do I configure it? | 17:07:30 |
| K900 | Uhhhh | 17:07:36 |
| K900 | Yes and uhhhh | 17:07:38 |
| K900 | Somewhere | 17:07:42 |
| ElvishJerricco | it's just a GHC build so it's within what I find acceptable | 17:07:48 |
| ElvishJerricco | ugh this is the biggest problem with hydra. Zero documentation, even for basic shit like "how do I increase the size limit" | 17:08:47 |
| ElvishJerricco | after grepping some code, I think it's max_output_size in the config file | 17:14:22 |
| ElvishJerricco | nixos's infra is open source, isn't it? I'm guessing it sets max_output_size somewhere? | 17:18:23 |
 ma27 | https://github.com/NixOS/infra/blob/33c54eca931a3435776308f8117850dda5912b48/delft/hydra.nix#L58 | 17:18:56 |
| ElvishJerricco | huh, only 3GB | 17:19:41 |
 cransom | fwiw, these were my tunings back when i was using hydra and it was creating (larger) disk images:
462 max_output_size = ${builtins.toString (1024 * 1024 * 1024 * 16)}
463 #512 megs of logs
464 max_log_size = ${builtins.toString (1024 * 1024 * 512)}
465 #nar_buffer_size = ${builtins.toString (1024 * 1024 * 1024 * 6)}
| 17:19:43 |
| ElvishJerricco | so I guess GHC is really cutting it close | 17:19:46 |
| ElvishJerricco | cransom: What is nar_buffer_size? | 17:20:25 |
| ma27 | IIRC it was increased for ghc in the past already? | 17:20:36 |
| ElvishJerricco | * huh, only 3GiB | 17:20:48 |
| cransom | that's a good question. its commented out so it seems i didn't need it. | 17:20:49 |
| ElvishJerricco | it doesn't grep in the hydra repo so maybe it's an old thing that got removed | 17:21:19 |
| ElvishJerricco | In reply to @ma27:nicht-so.sexy
IIRC it was increased for ghc in the past already? oof | 17:21:29 |
| ElvishJerricco | actually... nix path-info -h -s says GHC is only 1.7G, which is below the default max_output_size | 17:23:32 |
| ElvishJerricco | so that's weird | 17:23:38 |
| ElvishJerricco | yea, even the build in my hydra is 1.6G, which is unexpectedly slightly smaller, but more importantly still below the default max_output_size of 2 << 30 | 17:27:43 |
| ElvishJerricco | I guess we'll see if increasing max_output_size to 16G does the trick | 17:29:09 |
| cransom | i also ran into hijinx with auto-optimise-store with reporting output sizes, if you have that enabled. though, iirc, that was with disk image projected size rather than general outputs. or if you might be running a compressed fs | 17:40:10 |
| ElvishJerricco | cransom: hm that might be confusing things | 17:52:26 |
