| 1 Dec 2024 |
|  shawn8901 left the room. | 00:08:09 |
| shawn8901 joined the room. | 00:11:06 |
| 3 Dec 2024 |
|  stigo changed their display name from stigo (away) to stigo. | 00:52:15 |
|  femsci joined the room. | 05:01:10 |
| 4 Dec 2024 |
|  rhelmot joined the room. | 15:42:59 |
| rhelmot | I'm trying to run hydra with a diverted store but the gcroot management seems to be hardcoded for a non-diverted store. is there something I'm missing or do I need to start patching? | 15:54:34 |
 @rick:matrix.ciphernetics.nl | Likely you need to patch that, but maybe read the hydra tests to see how they handle this? | 16:20:01 |
 ma27 | fwiw I wrote a patch for this a while ago: https://github.com/NixOS/hydra/pull/1360 | 16:24:15 |
|  @belak:matrix.org left the room. | 17:39:24 |
| rhelmot | that looks like it's just replacing the local store with the remote store, which is not an option that I'm using right now - should I be? | 20:03:42 |
| rhelmot | I've just been setting store = daemon?real=/nix/hydra-store | 20:04:05 |
| rhelmot | or local?real=/nix/hydra-store in the daemon process | 20:04:20 |
| rhelmot | unless store and store_uri are synonyms...? | 20:04:41 |
| 5 Dec 2024 |
 hexa | does hydra gc build logs ever? 😄 | 11:11:20 |
| hexa | because h.n.o has like 420 GB worth of build logs and that feels a wee bit heavy | 11:11:58 |
| @rick:matrix.ciphernetics.nl | I don't think it does. | 13:11:33 |
 @janne.hess:helsinki-systems.de | In reply to @hexa:lossy.network
does hydra gc build logs ever? 😄 no | 13:31:34 |
| @janne.hess:helsinki-systems.de | but you should just be able to compress them | 13:31:42 |
| @janne.hess:helsinki-systems.de | depending on your version even with zstd | 13:31:57 |
| hexa | they are bz2 compressed | 13:32:55 |
| hexa | * they are bz2 compressed | 13:33:01 |
| hexa | and then zfs comes and compresses that again to 1.08x | 13:33:18 |
| hexa | so I think the best outcome would be to prune those older than say 3 years? | 13:33:42 |
 toonn | With fs compression enabled isn't the file-level compression counterproductive? | 14:22:47 |
| hexa | The zfs compression is "on" | 14:44:28 |
| hexa | That should be dirt cheap | 14:44:36 |
| hexa | But yeah, ideally don't compress and compress the fs with zstd-19 | 14:45:36 |
| @rick:matrix.ciphernetics.nl | In reply to @hexa:lossy.network
so I think the best outcome would be to prune those older than say 3 years? I wouldn't mind that, only recent logs are typically accessed | 15:03:34 |
| @rick:matrix.ciphernetics.nl | And people may always rebuild themselves to generate the logs | 15:03:49 |
 vcunat | Aren't they in S3 as well? | 16:36:30 |
