!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

482 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.151 Servers

Load older messages


SenderMessageTime
27 Jun 2026
@hexa:lossy.networkhexaRedacted or Malformed Event14:11:55
@emilazy:matrix.orgemilygoing to supported but not required makes sense to me then. I wonder if it makes sense to slightly decrease the per-job core count at the same time in exchange for the extra jobs you get. (sorry, this is just curiosity on my part, not trying to meddle with the decisions :) )14:14:35
@sempiternal-aurora:matrix.orgMyriaUhhh, it seems the problems I had with stdenv on the gcc-15.3.0 changes is also affecting staging-next. gfortran is failing build on aarch64-darwin (https://hydra.nixos.org/build/333247000) but locally it builds for me whe I ignore the cache14:16:46
@sempiternal-aurora:matrix.orgMyriaActually, may just be a gc error14:17:43
@sempiternal-aurora:matrix.orgMyriaBut this likely causes a large amount of failures14:18:00
@hexa:lossy.networkhexa

/nix/var/nix/builds/nix-48411-3267833365/build/./prev-gcc/as: line 141: exec: /nix/store/yn81qpksaxk576qb807fsck5ch7zmj6c-clang-wrapper-21.1.8/bin/as: cannot execute: No such file or directory

14:18:09
@k900:0upti.meK900Restarted, for now14:18:09
@k900:0upti.meK900 Mic92 do we have anything for the GC errors yet? 14:18:18
@k900:0upti.meK900Cause I feel like this cycle will be heck14:18:26
@hexa:lossy.networkhexabumped14:18:34
@k900:0upti.meK900If we have to deal with this the entire time14:18:46
@hexa:lossy.networkhexahttps://github.com/NixOS/infra/pull/1104 was supposed to resolve that iirc14:19:15
@emilazy:matrix.orgemilywhy is it only happening on Darwin(?)14:21:27
@k900:0upti.meK900It's not14:21:49
@k900:0upti.meK900But the darwins are slower so more likely to hit it14:21:56
@emilazy:matrix.orgemily

the darwins

you mean the Darwin

14:22:22
@hexa:lossy.networkhexagc is hourly on linux14:22:43
@hexa:lossy.networkhexaand twice per hour on darwin14:22:47
@hexa:lossy.networkhexa🤡14:22:50
@emilazy:matrix.orgemilydo we really need to GC that often?14:23:24
@hexa:lossy.networkhexawe can try and reduce14:23:56
@k900:0upti.meK900I assume those have less disk also?14:23:57
@emilazy:matrix.orgemilyoh I just mean in general14:24:03
@hexa:lossy.networkhexabut fixing gc was annoying for the small macs with little disk14:24:08
@hexa:lossy.networkhexathe linux builders have between 2x2 and 2x4TB NVME14:24:46
@hexa:lossy.networkhexathe macs have like 256 for the hetzner ones14:24:58
@hexa:lossy.networkhexaand more for the oakhost ones14:25:04
@hexa:lossy.networkhexawe can try fast-nix-gc14:26:19
@hexa:lossy.networkhexawhat would it fix? I guess gcing faster would be benefitial to the nodes anyhow14:26:59
@hexa:lossy.networkhexabut the window during which we'd gc would become smaller14:27:10

Show newer messages


Back to Room ListRoom Version: 6