!UNVBThoJtlIiVwiDjU:nixos.org

Staging

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

You have reached the beginning of time (for this room).


SenderMessageTime
12 Oct 2025
@emilazy:matrix.orgemily can be useful, OTOH is in tension with moving variant package sets to variants.nix which we'd generally like to do. 17:13:44
@emilazy:matrix.orgemilyit depends a bit on just how "expected" it is I think17:14:09
@emilazy:matrix.orgemily like "would people be okay with an update being held back just because it regresses pkgsStatic for that package" 17:14:27
@emilazy:matrix.orgemilyif it's part of a channel blocker then certainly17:14:33
@matthewcroughan:defenestrate.itmatthewcroughanI don't want things to be held back, but it would be nice if as much as possible was cached, and that status could be checked17:14:51
@ihar.hrachyshka:matrix.orgIhar Hrachyshkaaren't passthru.tests already kinda advisory? (I don't think we gate on them and I don't see a lot of nixpkgs-reviews ran with -p passthru.tests )17:15:25
@matthewcroughan:defenestrate.itmatthewcroughan K900: Can I merge https://github.com/NixOS/nixpkgs/pull/451338 when ready? It's what I intended now that it's musl conditional 17:18:40
@emilazy:matrix.orgemilycaching is unlikely to happen17:18:57
@emilazy:matrix.orgemily I think if passthru.tests.X fails you're meant to be worried, at least. 17:19:12
@matthewcroughan:defenestrate.itmatthewcroughanI mean I've been doing an okay job warming up my own caches by doing as many builds as possible, at all times 17:19:23
@emilazy:matrix.orgemily as in, you would usually add something to passthru.tests if it failing would be a reason for you to at least consider blocking the PR. 17:19:29
@matthewcroughan:defenestrate.itmatthewcroughan nix build .#checks.aarch64-linux.{base,musl,musl-llvm,gnu-musl} --keep-going for example 17:19:37
@matthewcroughan:defenestrate.itmatthewcroughanin my flake17:19:39
@matthewcroughan:defenestrate.itmatthewcroughanso I'll let those build on a bunch of builders 24/7 as I make changes to files.. and it's better than if I hadn't attempted the builds at all17:19:54
@matthewcroughan:defenestrate.itmatthewcroughansince at least then the base toolchains and stuff are cached17:20:43
@matthewcroughan:defenestrate.itmatthewcroughanI spent a few hours to build https://github.com/NixOS/nixpkgs/pull/45127419:58:11
@matthewcroughan:defenestrate.itmatthewcroughanonly thing blocking my little tracking flake, so I'm going to merge it?19:58:19
@matthewcroughan:defenestrate.itmatthewcroughanand it's conditional on musl, so no mass rebuilds 19:58:27
@matthewcroughan:defenestrate.itmatthewcroughanI don't know if I understand nixpkgs-review though, why does it say it only built the nixpkgs-manual19:59:02
@lt1379:matrix.orgLunIt only diffs things marked recurseForDerivations, pkgsMusl isn't and nothing that is depends on pkgsMusl.systemd.20:01:16
@matthewcroughan:defenestrate.itmatthewcroughanYeah I just wanted to use it for concrete testing that merging doesn't break anything by accident, which is obvious based on the diff, but I just do it anyway to check20:01:58
@lt1379:matrix.orgLun You can -p pkgsMusl.systemd (repeatable arg) to nixpkgs-review to get it to test attrs that the eval compare doesn't find 20:02:59
@matthewcroughan:defenestrate.itmatthewcroughanAh nice, I was looking for how to tell nixpkgs-review to do it anyway 20:03:28

Show newer messages


Back to Room ListRoom Version: 6