!UNVBThoJtlIiVwiDjU:nixos.org

Staging

311 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/108 Servers

Load older messages


SenderMessageTime
26 Nov 2025
@k900:0upti.meK900And the number of shares is kind of arbitrary and irrelevant17:16:54
@whispers:catgirl.cloudwhispers (it/fae)i have been curious, how do y'all actually monitor the status of a staging cycle? is it through the eval results at e.g. https://hydra.nixos.org/eval/1820494 or…?17:18:45
@k900:0upti.meK900Basically that yes17:18:59
@marcusramberg:matrix.orgMarcusI imagine not a lot of folks want to touch the hydra code base to improve it, given it's catalyst 🙂17:19:57
@vcunat:matrix.orgvcunatThe PRs have some further useful links: https://github.com/NixOS/nixpkgs/pull/46451217:36:05
@grimmauld:m.grimmauld.deGrimmauld (any/all) joined the room.18:09:23
@ysun:beeper.comYifei Sun joined the room.22:32:13
@stepbrobd:matrix.org@stepbrobd:matrix.org left the room.22:32:18
@shamrocklee:matrix.orgShamrockLee (Yueh-Shun Li)

Dear staging experts,

I'm authoring a rustPlatform.buildRustPackage fix that passes RUSTFLAGS only if specified or needed to prevent shadowing other *_RUSTFLAGS environment variables. (This partially restore the behavior before PR NixOS/nixpkgs#435278.)

Should I choose staging-next as its target branch for this fix? Since the issue also affects the Nixpkgs 25.11 release, should I backport with the backport staging-25.11 label?

https://github.com/NixOS/nixpkgs/pull/464707

22:50:24
@leona:leona.isleona staging-next and staging currently don't make a difference time-wise, so for more clarity I suggest staging. 23:05:01
@leona:leona.isleonaAs this is currently broken in 25.11, a backport to staging-25.11 should also be justified, yes23:05:57
27 Nov 2025
@conatsera:matrix.orgconatsera joined the room.01:16:52
28 Nov 2025
@grimmauld:m.grimmauld.deGrimmauld (any/all) changed their display name from grimmauld (any/all) to musl-official | Grimm | any/all.11:35:37
@grimmauld:m.grimmauld.deGrimmauld (any/all) changed their display name from musl-official | Grimm | any/all to Grimmauld (any/all).11:36:00
@k900:0upti.meK900 @Yureka (she/her) do you have a consistent repro for the Asahi crash? 18:37:09
@yuka:yuka.devYureka (she/her)use firefox18:37:29
@yuka:yuka.devYureka (she/her)browse the web18:37:32
@yuka:yuka.devYureka (she/her)it happens consistently after 5-10 min18:37:41
@k900:0upti.meK900Yeah I was hoping for something smaller maybe18:37:46
@yuka:yuka.devYureka (she/her)(also earlier, but at the latest 5-10min)18:37:52
@yuka:yuka.devYureka (she/her)I don't think anyone has another repro yet18:38:14
@k900:0upti.meK900 Can you try running it with GALLIUM_REFCNT_LOG=1? 18:38:16
@k900:0upti.meK900 Can you try running it with GALLIUM_REFCNT_LOG=refcnt.log? 18:38:36
@dramforever:matrix.orgdramforeverso i can reproduce it but don't get the file anywhere with this...23:51:17
29 Nov 2025
@ghpzin:envs.netghpzin It needs debug build (in case it was not one), do not think that env var does anything otherwise:
https://gitlab.freedesktop.org/mesa/mesa/-/blob/mesa-25.3.0/src/gallium/auxiliary/util/u_debug_refcnt.c#L27
00:57:22
@vcunat:matrix.orgvcunat Now I added a gcc15 jobset/eval, as the queue had basically just darwin stuff. 08:59:53
@vcunat:matrix.orgvcunat(I'll micromanage if need be, so that it won't slow down e.g. 25.11 builds significantly.)09:00:28
@dramforever:matrix.orgdramforeveroh no, oh no i can count the frames now... and it stopped crashing, perhaps because it's not rendering many frames to begin with?13:01:59
@dramforever:matrix.orgdramforeveractually i'm going to try running the debug build without refcnt log13:04:29
@dramforever:matrix.orgdramforeverwould be interesting if it stops crashing13:04:43

Show newer messages


Back to Room ListRoom Version: 6