!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

385 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.116 Servers

Load older messages


SenderMessageTime
8 Mar 2026
@eveeifyeve:matrix.orgeveeifyeveA good tip, sometimes you need to take it easy on yourself..12:32:40
@eveeifyeve:matrix.orgeveeifyeve* A good tip, sometimes you need to take it easy on yourself and take a break.12:33:05
@hexa:lossy.networkhexa (signing key rotation when) you can open a ticket with fastly here https://support.fastly.com/s/contactsupport 13:23:58
@hexa:lossy.networkhexa (signing key rotation when)this is better than us opening one, since you can collect the details and reproduce the issue13:24:26
@ss:someonex.netSomeoneSerge (matrix works sometimes) changed their display name from SomeoneSerge (back on matrix) to SomeoneSerge (matrix works sometimes).23:34:24
10 Mar 2026
@amadaluzia:unredacted.orgamadaluzia joined the room.01:46:02
@picnoir:alternativebit.frPicnoir👋 triton-llvm is currently failing on hydra for aarch64 with "output limit exceeded": https://hydra.nixos.org/build/323005905 x86 seems fine https://hydra.nixos.org/build/323005904 The embeddings are pretty big :/ This is a pretty expensive package to build, is there a way to increase this limit without splitting this package?16:39:05
@hexa:lossy.networkhexa (signing key rotation when)Already poked serge a week ago or so 😬16:51:59
@hexa:lossy.networkhexa (signing key rotation when)It does affect a package I maintain, but that's hardly good enough a reason to bump the limit.16:52:33
@hexa:lossy.networkhexa (signing key rotation when)Someone needs to answer the question why it is bigger on arm than x86 and by how much16:53:03
@hexa:lossy.networkhexa (signing key rotation when)And ideally show growth over time16:53:15
@lt1379:matrix.orgLunI can take a look17:07:38
@picnoir:alternativebit.frPicnoirSize-wise, it seems to progressively grow: https://hydra.nixos.org/job/nixos/unstable/nixpkgs.triton-llvm.aarch64-linux#tabs-charts17:13:09
@picnoir:alternativebit.frPicnoirNearly doubled in 2 years.17:13:17
@hexa:lossy.networkhexa (signing key rotation when) Would be annoying to give it a chance and it continues the growth 18:05:08
@picnoir:alternativebit.frPicnoirThat's the likely outcome :)18:18:52
@picnoir:alternativebit.frPicnoirThe x86 variant suffers from the same symptoms. It's a matter of time before it reaches the 4GB limit as well.18:19:36
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Eh ok you nerd sniped me and it seems that a bunch of binaries are huge because they link statically to mlir libraries?18:38:53
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)I’m not familiar with the package but I can try poking and see if one can build with shared libs18:41:42
@glepage:matrix.orgGaétan Lepage FYI: https://github.com/NixOS/nixpkgs/pull/497817#issuecomment-4033492850 18:48:35
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)
In reply to @xokdvium:matrix.org
I’m not familiar with the package but I can try poking and see if one can build with shared libs
Building with BUILD_SHARED_LIBS now. Will report once (looks at the builds logs) whopping 7k objects are built
18:52:02
@lt1379:matrix.orgLunMight prefer LLVM_TOOL_LLVM_DRIVER_BUILD, iirc there was some cursed issue with multiple differing llvms in the same process with shared libs when you got further out to things like torch.19:16:54
@lt1379:matrix.orgLunthat only saves about 500MiB :c19:28:40
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)for x86-linux the diff is 1.8G -> 200M19:47:17
@lt1379:matrix.orgLun* that (LLVM_TOOL_LLVM_DRIVER_BUILD) only saves about 500MiB :c19:49:06
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Ah yeah, but having a static and a shared library in the same process is even more cursed.19:51:16
@lt1379:matrix.orgLunIf you put something up give me a ping so I can test some leaf packages with highest chance of hitting the cursed19:53:29
@hexa:lossy.networkhexa (signing key rotation when) The answer is always: reluctantly 19:55:31
@hexa:lossy.networkhexa (signing key rotation when)And most of the time for the graphical ISO19:55:52
@hexa:lossy.networkhexa (signing key rotation when)We've not established precedent for AI/ML packages and that's a good thing19:56:21

There are no newer messages yet.


Back to Room ListRoom Version: 6