!UNVBThoJtlIiVwiDjU:nixos.org

Staging

317 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen109 Servers

Load older messages


SenderMessageTime
21 Nov 2025
@uep:matrix.orguepI just did this.. guess i'll try the patch against current unstable instead10:40:30
@k900:0upti.meK900All that stuff should be cached on next10:42:38
@k900:0upti.meK900So whatever rebuilds you're getting are from the gtk update10:42:47
@k900:0upti.meK900Sadly10:42:47
@k900:0upti.meK900Maybe just try running less builds at a time10:42:58
@k900:0upti.meK900They tend to be weirdly timing sensitive10:43:06
@uep:matrix.orguepit's trying a lot in parallel.. 36c/72t makes it greedy i guess10:44:15
@uep:matrix.orguepnah, gjs blows up every time10:56:35
@uep:matrix.orguep
   > Gjs-Message: 10:54:41.636: Profiler started
   > Gjs-Message: 10:54:41.636: Profiler stopped
   > Trace/breakpoint trap (core dumped)
   > Trace/breakpoint trap (core dumped)
   >
   > (gjs-console:2804): Gjs-CRITICAL **: 10:54:42.406: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
   > The offending callback was destroy(), a vfunc.
   > == Stack trace for context 0x5555555b36c0 ==
   > Gjs-Message: 10:54:42.497: Wrote coverage statistics to /build/gjs-1.86.0/build/coverage.lcov
   > Trace/breakpoint trap (core dumped)
10:57:45
@uep:matrix.orguepyuck10:57:47
@uep:matrix.orguepgoing to try building just staging-next first11:01:15
@vcunat:matrix.orgVladimír ČunátYou're atop staging-next now?11:02:06
@vcunat:matrix.orgVladimír Čunát

So the gjs build is this one?

/nix/store/p8qi0c1z1mv0x67pwd9p0s64y4dsma9z-gjs-1.86.0.drv
11:02:16
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) i do in theory have 5 builders and intel igpu, i do not have to build musl... What is it you need to test? Just gtk4 apps? 11:02:17
@k900:0upti.meK900Yes11:02:22
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)does my system mesa also need to be from staging-next ?11:03:51
@k900:0upti.meK900No11:04:00
@k900:0upti.meK90025.3 from master is fine11:04:03
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)is zenity enough to reproduce whatever issues?11:04:58
@vcunat:matrix.orgVladimír Čunátstaging-next has the advantage that it gets more things in cache (assuming you do the gtk4 update)11:05:06
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)its the cheapest gtk4 app one can build11:05:13
@uep:matrix.orgueperror: Cannot build '/nix/store/p8qi0c1z1mv0x67pwd9p0s64y4dsma9z-gjs-1.86.0.drv'. 11:05:29
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)actually zenity on staging-next is already cached11:05:34
@uep:matrix.orguepyep, that's the one, and it dies in plain staging-next too11:05:42
@vcunat:matrix.orgVladimír Čunátyou can download it: https://hydra.nixos.org/build/31411019811:05:53
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)launches for me11:06:18
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)image.png
Download image.png
11:06:19
@uep:matrix.orguepbitten by negative cache i guess, but i'm more worried why it's failing11:06:23
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)just current staging-next11:06:37
@vcunat:matrix.orgVladimír Čunát(I don't know what's wrong with the build, but it's surely unrelated to the issue at hand.)11:06:38

Show newer messages


Back to Room ListRoom Version: 6