!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

408 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.127 Servers

Load older messages


SenderMessageTime
27 Apr 2026
@vcunat:matrix.orgvcunat* I'd say that if a build without the flag takes hours and the flag speeds it up very significantly, we'd better add the flag.14:28:31
@vcunat:matrix.orgvcunat* I'd say that when a build without the flag takes hours and the flag speeds it up very significantly, we'd better add the flag.14:28:39
@mynacol:mynacol.xyzmynacolOr just increase the the timeout. (My compiles with 32 core somewhat older intel take 30 min for rusty-v8 and 1h for deno, and for comparison 1-2h (depending on pgo double-runs) on mullvad-browser)14:28:53
@mynacol:mynacol.xyzmynacol* Or just increase the timeout. (My compiles with 32 core ~~somewhat older~~ intel Xeon E5-2630 v3 take 30 min for rusty-v8 and 1h for deno, and for comparison 1-2h (depending on pgo double-runs) on mullvad-browser)14:32:20
@ninja:worldethicaldataforum.orgNinja joined the room.14:37:10
@mynacol:mynacol.xyzmynacolThe funny thing is that the builds are at those points rather single-threaded (only one or two hefty crates). So I look into the timeout instead: https://github.com/NixOS/nixpkgs/pull/51405714:51:28
28 Apr 2026
@aangularframework:matrix.orgAangularity joined the room.04:39:30
29 Apr 2026
@purepani:matrix.orgpurepani joined the room.04:23:10
@ihar.hrachyshka:matrix.orgIhar Hrachyshka @mynacol:mynacol.xyz: increasing timeouts per package may not actually work because of a bug in nix, see https://github.com/NixOS/infra/pull/950 11:17:04
30 Apr 2026
@isabel:isabelroses.comisabel changed their profile picture.18:46:58
@syntheit:matrix.orgDaniel joined the room.23:24:25
2 May 2026
@tom:dragar.deTom changed their profile picture.18:41:01
3 May 2026
@isabel:isabelroses.comisabel changed their profile picture.10:38:42
4 May 2026
@wegank:matrix.org@wegank:matrix.org left the room.00:24:04
@hexa:lossy.networkhexa (signing key rotation when)who created https://hydra.nixos.org/jobset/nixos/disable-nix-in-nixos-tests?23:57:08
@hexa:lossy.networkhexa (signing key rotation when)https://github.com/NixOS/nixpkgs/pull/51664523:57:51
@hexa:lossy.networkhexa (signing key rotation when)would have loved some coordination here23:57:57
@hexa:lossy.networkhexa (signing key rotation when)for one thing we have a release schedule to keep23:58:26
5 May 2026
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)And security releases to build?00:07:01
@hexa:lossy.networkhexa (signing key rotation when)yeah, we can manually prioritize, but still00:07:27
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Tbh this is relatively easy to just do locally on a beefy enough machine, wth00:08:12
@joerg:thalheim.ioMic92I did this sorry. I cancelled both for now. When is a good time for this?05:36:38
@hexa:lossy.networkhexa (signing key rotation when)That's a good question.12:13:27
@hexa:lossy.networkhexa (signing key rotation when) vcunat wdyt 12:13:32
@vcunat:matrix.orgvcunat I wonder. Often at the end of a staging-next* cycle we would be left with a day or two of free *-linux capacity (waiting for *-darwin), though this time it didn't really happen. 12:21:04
@hexa:lossy.networkhexa (signing key rotation when)yeah, this time was probably eaten by nix updates12:21:29
@vcunat:matrix.orgvcunatRebuilding all NixOS tests can easily take a day or two.12:21:56
@vcunat:matrix.orgvcunatFor a single jobset even.12:22:02
@hexa:lossy.networkhexa (signing key rotation when)why was nixos/unstable canceled?17:22:36
@hexa:lossy.networkhexa (signing key rotation when) vcunat? 17:23:13

Show newer messages


Back to Room ListRoom Version: 6