!UNVBThoJtlIiVwiDjU:nixos.org

Staging

390 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/127 Servers

Load older messages


SenderMessageTime
22 Jun 2026
@vcunat:matrix.orgVladimír Čunát(or whatever is slowing it down at this very moment)13:41:06
@hexa:lossy.networkhexaif we only schedule 4 steps in 30s that is bad for big closures with many small files13:41:21
@vcunat:matrix.orgVladimír Čunát* (or whatever is slowing it down at this very moment, e.g. on nixos-26.05)13:41:23
@hexa:lossy.networkhexaRedacted or Malformed Event13:41:29
@vcunat:matrix.orgVladimír Čunát* (or whatever is slowing it down at this very moment, e.g. on https://hydra.nixos.org/jobset/nixos/release-26.05 )13:41:52
@vcunat:matrix.orgVladimír ČunátStill, "Steps completed per minute" metric shows much higher than with the old queue-runner.13:42:53
@vcunat:matrix.orgVladimír ČunátSo even this phase is probably significantly faster than it used to be.13:43:28
@qyliss:fairydust.spaceAlyssa Rosshave we still not disabled the non-blocker NixOS tests?13:44:10
@grimmauld:m.grimmauld.deGrimmauld (any/all)also don't forget we recently killed half the nixos tests13:44:16
@vcunat:matrix.orgVladimír ČunátWe haven't. I've had too many other higher-priority tasks so far.13:44:44
@grimmauld:m.grimmauld.deGrimmauld (any/all)I meant killing the all-drivers tests (https://github.com/NixOS/nixpkgs/pull/532396)13:45:42
@vcunat:matrix.orgVladimír ČunátYes, I know, but I don't expect it helped dramatically with building all those etc and disk-image derivations.13:46:32
@k900:0upti.meK900Emily wanted to do it in the jobset unification PR13:46:49
@vcunat:matrix.orgVladimír ČunátBecause these drivers still do get run.13:46:50
@hexa:lossy.networkhexawe don't understand the impact of container tests yet, do we?13:46:54
@emilazy:matrix.orgemilyhave local WIP with jobset merge14:35:03
@emilazy:matrix.orgemily so still with x86_64-darwin drop but avoiding any mass rebuilds in the process? I can split up my branch a little for that 14:37:58
@emilazy:matrix.orgemilyI'm a bit confused by the purported upper bound on the rebuilds though14:38:28
@emilazy:matrix.orgemilythe PR has rebuild Darwin stdenv label14:38:32
@k900:0upti.meK900Scratch that, we don't have enough pnpm for this to need staging14:41:05
@hexa:lossy.networkhexaokay, master14:42:00
@hexa:lossy.networkhexaRedacted or Malformed Event14:42:12
@vcunat:matrix.orgVladimír ČunátProbably, but it's mainly up to you.14:45:02
@vcunat:matrix.orgVladimír ČunátThat's because the CI takes an "incorrect" comparison base.14:45:21
@vcunat:matrix.orgVladimír ČunátWe'll be reusing 26.05 builds, not unstable/master builds14:45:33
@emilazy:matrix.orgemily ah, makes sense. it's almost master sized then, right? as in, it's a number of rebuilds we might have in flight from a few unfortunately large-rebuild master bumps in a row 14:49:55
@emilazy:matrix.orgemily(I agree w/ ^ but to be fair dropping a platform will make the numbers on that hard to compare anyway)14:50:42
@k900:0upti.meK900I mostly care about Linux numbers tbh14:50:58
@emilazy:matrix.orgemilybut the thing you're measuring based on, the queue resource, is shared between the platforms14:57:42
@emilazy:matrix.orgemilyso fewer Darwin jobs is a confounder14:57:51

Show newer messages


Back to Room ListRoom Version: 6