| 7 Jun 2024 |
 Atemu | You need to migrate the disk state to the new keys though | 08:32:24 |
| Atemu | There's an installable zip somwhere which can do this | 08:34:11 |
 jaen | Atemu: is there anything else blocking https://github.com/nix-community/robotnix/pull/236 or could we maybe merge it? I have also rebased https://github.com/nix-community/robotnix/pull/237 on top of it (and used the commit format you seem to prefer). Hopefully it will be easier to merge (unless there's something we'd want to wait for before it?). I have also finally made a PR for the changes to re-enable basic CI (https://github.com/nix-community/robotnix/pull/239), but that might require some more discussion. | 11:30:04 |
| Atemu | No, just me needing to find the time to take a proper look | 14:10:37 |
 erahhal | I occasionally get ninja: build stopped: subcommand failed. I assume this is due to lack of resources, as it happens less when I unload all desktop apps, and also it's non-deterministic and doesn't seem to be associated with a particular compilation failure. Tried using the -j and --cores flags with nix build. Any other tips to address this? My machine as 32gb memory and 12 cores. | 15:37:41 |
| jaen | If you have /tmp backed by tmpfs you might want to either buy 3x more RAM or back it by a block device. If you don't, then I'm not sure what that could be off-hand | 15:42:44 |
| jaen | * If you have /tmp backed by tmpfs you might want to either buy 3x more RAM or back it by a block device instead. If you don't, then I'm not sure what that could be off-hand | 15:43:03 |
| erahhal | thx. Doesn't appear to be using tmpfs. | 15:54:26 |
| Atemu | erahhal: Check dmesg whether the OOM killer reaped a process | 16:12:05 |
| Atemu | Make sure you have swap | 16:12:16 |
| Atemu | Even with 32G | 16:12:37 |
| erahhal | Yup, got swap | 16:32:18 |
 eyJhb | zramswap! That's what saved my life | 16:34:13 |
| erahhal | thank you i will try that! | 16:38:02 |
| Atemu | Don't combine zram and physical swap | 16:39:16 |
| erahhal | Ok, definitely wont | 16:41:04 |
| erahhal | I'm using zfs btw, wonder if it's related | 16:45:31 |
| Atemu | I had Android builds trigger ZFS incompatibilities with newer kernels before | 16:46:54 |
| Atemu | Again, check dmesg whether an OOM event occured first | 16:47:05 |
| erahhal | No OOMs | 16:48:39 |
| Atemu | Then check the logs why it's actually failing | 16:48:53 |
| Atemu | Which kernel are you ono? | 16:48:58 |
| Atemu | * Which kernel are you ono | 16:49:00 |
| Atemu | * Which kernel are you on? | 16:49:04 |
| erahhal | A lot of these: [103533.864202] systemd-journald[1122]: Under memory pressure, flushing caches. | 16:49:16 |
| erahhal | Redacted or Malformed Event | 16:49:22 |
| erahhal | 6.8 | 16:49:26 |
| erahhal | Nothing in build logs other than the ninja line above | 16:49:53 |
| Atemu | There is, just further up | 16:50:07 |
| erahhal | No, I lied, I found an OOM in dmesg | 16:50:45 |
