| 3 Apr 2026 |
 emily | though doesn't this imply that our own libxml2 will also clash? 🫠 | 23:15:49 |
| emily | (allow file-read* (subpath "/usr/share/locale")) | 23:16:09 |
| emily | IIRC it's been allowed for a long time | 23:16:33 |
 Randy Eckenrode | ICU needs /usr/share/icu. | 23:16:49 |
 hexa | ok, log erase --all might just go in a launchd timer | 23:17:12 |
| hexa | yeah, it's funny how greedy apple is with cores | 23:17:27 |
| hexa | how else are we supposed to slice them up then? | 23:17:43 |
| emily | hmm are they? I feel like the average Windows ultrabook doesn't ship with 10 cores of anything but maybe I'm behind the times :) | 23:21:12 |
| emily | at the high end ofc is a different matter | 23:21:22 |
| emily | but direction there is very much towards clusters (e.g. there's RDMA over Thunderbolt now) | 23:21:42 |
| hexa | right, I'm probably comparing apples and oranges | 23:21:45 |
| emily | well tbh I guess with 5 + 5 you might get both using 4 P + 1 E which would be just fine | 23:22:44 |
| emily | er | 23:22:57 |
| emily | sorry I mean 2 P + 3 E | 23:23:06 |
| emily | what I mean is that M4 → M4 Pro looks like just 10 cores → 12 cores | 23:23:27 |
| hexa | oh, but it has many more P cores | 23:23:38 |
| hexa | I see | 23:23:39 |
| emily | but it's actually 4P → 8P, 6E → 4E | 23:23:40 |
| hexa | good call | 23:23:47 |
| emily | also higher memory bandwidth etc. | 23:23:48 |
| emily | so the perf differential may be higher than you expect | 23:23:53 |
| hexa | that changes things quite a bit | 23:24:09 |
| emily | I would be tempted to say you do one big-parallel build per M4 or else two per M4 Pro, say | 23:24:20 |
| emily | https://browser.geekbench.com/v6/cpu/compare/17442341?baseline=17440508 M4 vs. M4 Pro benchmark fwiw (though Nixpkgs is not Geekbench and also RAM differs) | 23:26:04 |
| emily | the memory bandwidth helps it eke out a bit more even on single-core workloads | 23:26:33 |
| hexa | I hear you | 23:27:46 |
 EsperLily [she/her] | is there any way to ask hydra to just try rebuilding a package that failed? something called edencommon failed on aarch64-darwin https://hydra.nixos.org/build/324463608 but the failure is just a timeout running tests, so it's a nondeterministic failure. The consequence of this is watchman now also needs to be built from source. Trying to build this stuff locally I also got the timeout failure, but I just tried to build edencommon on its own and it worked, so it'd be nice to have hydra just try again (and build watchman too) | 23:49:37 |
| hexa | restarted | 23:54:33 |
| 4 Apr 2026 |
| emily | that failure happens a lot, we have a patch to increase the timeout but I guess it's not enough now somehow | 00:19:07 |
| emily | someone should probably look into it. some package maintainer of the package. certainly not me. I would never maintain that awful stack | 00:19:24 |
