!UNVBThoJtlIiVwiDjU:nixos.org

Staging

316 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
22 Sep 2025
@k900:0upti.meK900OK I think this actually does work06:38:54
@ofalvai:matrix.orgofalvai To be honest, I was building off a few days old staging and encountered the failure there. But now I see the failure in Hydra as well: https://hydra.nixos.org/build/308144224 06:42:30
@vcunat:matrix.orgVladimír ČunátThe error doesn't happen on x86_64-linux, so that can be confusing.06:47:02
@k900:0upti.meK900
/build/dotnet-9.0.110/eng/detect-binaries.sh: line 135: 5091 Segmentation fault /build/dotnet-9.0.110/.dotnet/dotnet run --project /build/dotnet-9.0.110/eng/tools/BinaryToolKit -c Release --property:RestoreSources=/nix/store/pir670rnvffbwf5jigw5zgm5c442z8px-dotnet-stage0-sdk-9.0.110-artifacts clean /build/dotnet-9.0.110 -o /build/dotnet-9.0.110/artifacts/log/binary-report -ab /build/dotnet-9.0.110/eng/allowed-sb-binaries.txt -l Debug -p CustomPackageVersionsProps=/nix/store/pir670rnvffbwf5jigw5zgm5c442z8px-dotnet-stage0-sdk-9.0.110-artifacts/PackageVersions.props
07:01:53
@k900:0upti.meK900So uhhh07:01:55
@k900:0upti.meK900Maybe we pin LLVM 20 lol07:01:59
@k900:0upti.meK900I'm going to try building it with LLVM 20 pinned07:11:56
@k900:0upti.meK900Well at least it doesn't just immediately segfault this time07:48:35
@k900:0upti.meK900OK yeah it definitely does not segfault on 2008:10:26
@k900:0upti.meK900So does anyone want to figure this out08:18:20
@k900:0upti.meK900Or should I just send it08:18:23
@k900:0upti.meK900Because it definitely works on 2008:18:28
@k900:0upti.meK900And it definitely doesn't on 2108:18:31
@vcunat:matrix.orgVladimír ČunátI'd say you send it. That won't prevent anyone from fixing it at any point in the future.08:22:16
@k900:0upti.meK900I'm going to let it finish building EVERYTHING just to be super sure08:23:15
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)Oh hey, libreoffice built on top of my libxml branch! Surprising!08:26:42
@k900:0upti.meK900 So does anyone want to rubber stamp https://github.com/NixOS/nixpkgs/pull/445006 before emily wakes up 08:28:37
@k900:0upti.meK900OK I am now officially running staging-next10:24:12
@k900:0upti.meK900And nothing seems to have exploded10:24:16
@wolfgangwalther:matrix.orgWolfgang Walther

I'm getting pinged for "is staging-next OK", we really need that @NixOS/staging team...

Can someone look at https://github.com/NixOS/nixpkgs/pull/445296 ?

19:10:16
@k900:0upti.meK900It's just the test driver19:12:42
@k900:0upti.meK900So definitely OK19:12:46
@k900:0upti.meK900Technically kernel-next but we don't have that yet do we19:12:52
@wolfgangwalther:matrix.orgWolfgang Walther I like kernel-next. I wonder what emily and ma27 say to that instead of this-branch-will-be-batched-with-kernel-updates. 19:16:38
@emilazy:matrix.orgemily it's not really anything like staging-next is it? but I'm checked out of the bikeshed discussion at this point :) 19:25:08
@wolfgangwalther:matrix.orgWolfgang Walther:D I don't care, the PRs with a branch name is already up, so all good.19:32:25
@wolfgangwalther:matrix.orgWolfgang Walther* :D I don't care, the PRs with a branch name are already up, so all good.19:32:32
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) emily: i am seeing obscure failures with nixd failing to find llvm via cmake. Considering i know nothing about llvm, i'll be deferring this one. Maybe you have an idea... 19:48:08
@emilazy:matrix.orgemilyLLVM 21 issue?19:49:07
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)maybe19:50:13

Show newer messages


Back to Room ListRoom Version: 6