!UNVBThoJtlIiVwiDjU:nixos.org

Staging

396 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/128 Servers

Load older messages


SenderMessageTime
26 Jun 2026
@hexa:lossy.networkhexaok, eager-heisenberg is now named21:08:48
@hexa:lossy.networkhexa kind-lumiere builds a llvvm 21:09:00
@hexa:lossy.networkhexaRedacted or Malformed Event21:09:02
@hexa:lossy.networkhexaRedacted or Malformed Event21:09:05
@emilazy:matrix.orgemilyfwiw I'm pretty sure desktop Linux has at least two of those hostname concepts :P21:38:16
@hexa:lossy.networkhexa

/nix/store/5vmd3cqj6skjajg0yj9jl8dsddwp0700-bash-5.3p9/bin/bash: line 1: /nix/store/v6zk257yx9736bpwf5jyl1v0y5pvydia-perl-5.42.0/bin/perl: No such file or directory

21:39:27
@hexa:lossy.networkhexasigh21:39:31
@hexa:lossy.networkhexathis is getting annoying fast21:39:46
@hexa:lossy.networkhexadraining for gc sounds really plausible right now21:41:05
@grimmauld:m.grimmauld.deGrimmauld (any/all)What i do wonder... The openmp thread hogging issues, why did they pop up now? Did they pop up because new hydra queue runner can actually keep up with supplying build machines fast enough? or is there some other reason?22:57:26
@grimmauld:m.grimmauld.deGrimmauld (any/all)* What i do wonder... The openmp thread hogging issues, why did they pop up now? Did they pop up because new hydra queue runner can actually keep up with supplying jobs to build machines fast enough? or is there some other reason?22:57:43
@grimmauld:m.grimmauld.deGrimmauld (any/all)I'd have expected this to be much more of a problem already22:58:22
@hexa:lossy.networkhexayeah, higher occupation22:58:27
@hexa:lossy.networkhexa https://grafana.nixos.org/d/mel9fqb/very-simple-combined-occupancy?orgId=1&from=now-30d&to=now&timezone=browser 22:58:52
@grimmauld:m.grimmauld.deGrimmauld (any/all)okay yeah adjusting the average to get less noise, we are seeing about the maximum occupation we had before only occasionally. Time will tell whether this will stay like that, but is already a quite interesting observation about new queue runner23:02:56
@grimmauld:m.grimmauld.deGrimmauld (any/all)image.png
Download image.png
23:02:56
@grimmauld:m.grimmauld.deGrimmauld (any/all)makes sense, ty :)23:03:41
@grimmauld:m.grimmauld.deGrimmauld (any/all)* okay yeah adjusting the average to get less noise, we are seeing about the maximum occupation we had only occasionally before. Time will tell whether this will stay like that, but is already a quite interesting observation about new queue runner23:04:26
@grimmauld:m.grimmauld.deGrimmauld (any/all)Actually I have an idea to get both data from the noisy and the long average with some nice extra info... Will build a graph for that tomorrow and see what I can observe with it23:17:16
@hexa:lossy.networkhexanew staging-next https://github.com/NixOS/nixpkgs/pull/53585523:17:18
@grimmauld:m.grimmauld.deGrimmauld (any/all)Damn, when was the last time vcunat didn't do the staging-next?23:19:04
@hexa:lossy.networkhexa oh no, the eval check for x86_64-darwin is failing 23:19:08
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+head%3Astaging-next+-author%3Avcunat+is%3Aclosed+in%3Atitle+staging-next+sort%3Acreated-desc+label%3A10.rebuild-linux-stdenv23:20:33
@hexa:lossy.networkhexait's been a while23:20:36
@grimmauld:m.grimmauld.deGrimmauld (any/all)Damn! One k900, and then 2023 before that. 3 years non-stop staging is a lot.23:21:44
27 Jun 2026
@hexa:lossy.networkhexa-63947, gg00:44:20
@debtquity:matrix.orgdebtquityfeels like this room hasn't stopped chatting for 48 hrs00:45:33
@opandddd:matrix.orgSapii/Sapersoninfra team hard at work 🫡00:57:08
@hexa:lossy.networkhexastaging is like the group of people who keep nixpkgs running00:57:43
@hexa:lossy.networkhexaRedacted or Malformed Event00:57:55

Show newer messages


Back to Room ListRoom Version: 6