| 16 Jul 2024 |
 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 |
| Traxys | Yeah the strange thing is that is does not seem to be deterministic, as when re-triggering the build the same derivation passed | 20:30:55 |
| magic_rb | Yeah this is recent, ill need @zowoq to pull the logs from the journal to see if anything pops up there. This is definitely a bug that needs fixing, if you could open a issue on the buildbot-nix repo id appreciate it | 20:32:38 |
| Traxys | I'll do that! | 20:33:12 |
| magic_rb | Thanks, if you run into anything which looks like a implementation bug ping me | 20:33:41 |
