| 16 Jul 2024 |
Soliprem | and hasn't had evaluation errors for me | 23:48:17 |
Soliprem | or at least in the meantime it can work as a substitute, maybe using the maximal config | 23:48:41 |
Soliprem | until nixvim is fixed | 23:48:52 |
zowoq | nixvim isn't broken, I was replying to the previous comment about the broken worker. | 23:50:56 |
Soliprem | In reply to @zowoq:matrix.org nixvim isn't broken, I was replying to the previous comment about the broken worker. oh sry | 23:51:07 |
zowoq | In reply to @glepage:matrix.org Cool ! You also have x86 machine(s) as well, right ? We don't have native x86 darwin but the aarch64 machine can emulate x86. | 23:54:09 |
| 17 Jul 2024 |
GaƩtan Lepage | Makes sense. Good to know, thanks ! | 06:07:19 |
Traxys | I tried to improve the situation for nixvim in 1882, empirically it seems to help as locally the build only seems to use 2-3 GiB of RAM, but I saw some error: writing to file: Broken Pipe in buildbot, I'm not sure what caused that :/ | 20:20:54 |
magic_rb | In reply to @traxys:familleboyer.net I tried to improve the situation for nixvim in 1882, empirically it seems to help as locally the build only seems to use 2-3 GiB of RAM, but I saw some error: writing to file: Broken Pipe in buildbot, I'm not sure what caused that :/ Im somewhat responsible for the recent buildbot work, ill try to identify where that came from, but my guess is that there is an empty attrset somewhere which buildbot did not agree with. No sure tho, ill take a definitive look tomorrow | 20:28:52 |