!UNVBThoJtlIiVwiDjU:nixos.org

Staging

337 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/111 Servers

Load older messages


SenderMessageTime
29 Dec 2025
@ghpzin:envs.net@ghpzin:envs.net true/false in stdbool.h are conditional on __STDC_VERSION__ > 201710L:
https://github.com/gcc-mirror/gcc/blob/1b995214830669b96a19a6b6463aa6c1647cea9b/gcc/ginclude/stdbool.h#L33
So you can safely include it.
In musl they are not:
https://git.musl-libc.org/cgit/musl/tree/include/stdbool.h
07:59:00
@ghpzin:envs.net@ghpzin:envs.net true/false in stdbool.h are conditional on __STDC_VERSION__ < 201710L:
https://github.com/gcc-mirror/gcc/blob/1b995214830669b96a19a6b6463aa6c1647cea9b/gcc/ginclude/stdbool.h#L33
So you can safely include it.
In musl they are not:
https://git.musl-libc.org/cgit/musl/tree/include/stdbool.h
07:59:31
@juliusfreudenberger:jfreudenberger.dejuliusfreudenbergerGo 1.24.11 would be there, which is required for teleport. But it is not security relevant, so I might just skip this last update for oldstable as well.14:26:48
@vcunat:matrix.orgvcunat The current release-25.05..staging-25.05 will probably never get merged anymore. 14:29:38
@vcunat:matrix.orgvcunat(i.e. no staging-next-25.05 cycle anymore)14:31:07
@juliusfreudenberger:jfreudenberger.dejuliusfreudenbergerThat's what I already figured. Thanks for clarifying nonetheless!14:36:35
@vcunat:matrix.orgvcunat staging-next-25.11 was running builds in backgroud for a few days already. Now I opened a PR:
https://github.com/NixOS/nixpkgs/pull/475079
15:53:15
@vcunat:matrix.orgvcunat * staging-next-25.11 has been running builds in backgroud for a few days already. Now I opened a PR:
https://github.com/NixOS/nixpkgs/pull/475079
15:54:50
30 Dec 2025
@vcunat:matrix.orgvcunat

I'm not sure about staging-next. While I'm not aware of any particular blockers, the amount of regressions does remain pretty high.

One way to look is https://hydra.nixos.org/eval/1821537?compare=unstable
i.e. 4.3k jobs newly failing - 1.1k newly succeeding. If we wanted to take into account the rotation of non-default python version (which appear as new and removed packages in there), we could look at total successes and failures.

Successes decrease by 15k (!) and failures increase by 7k.

07:43:57
@vcunat:matrix.orgvcunat(PRs currently open against staging-next seem to fix at most a couple hundred jobs)07:46:45
@vcunat:matrix.orgvcunat *

I'm not sure about staging-next. While I'm not aware of any particular blockers, the amount of regressions does remain pretty high.

One way to look is https://hydra.nixos.org/eval/1821537?compare=unstable
i.e. 4.3k jobs newly failing - 1.1k newly succeeding. If we wanted to take into account the rotation of non-default python version (which appear as new and removed packages in there), we could look at total successes and failures.

Successes decrease by 17k (!) and failures increase by 7k.

07:55:51
@k900:0upti.meK900I see a lot of potentially flaky stuff in the reports07:59:53
@k900:0upti.meK900twisted uvloop etc07:59:56
@vcunat:matrix.orgvcunatThey've been retried a few times already.08:00:37
@grimmauld:m.grimmauld.deGrimmauld (any/all)didn't hexa disable tests on uvloop darwin?08:00:54
@vcunat:matrix.orgvcunatIf they're that much flaky, I consider them as good as always failing.08:00:56
@grimmauld:m.grimmauld.deGrimmauld (any/all)but anyways, i vote to fix channel blockers only and other than that figure it out on master08:01:20
@hexa:lossy.networkhexaOn 3.1408:01:42
@vcunat:matrix.orgvcunaton x86_64-darwin only, right?08:02:24
@hexa:lossy.networkhexaBoth08:02:32
@vcunat:matrix.orgvcunatOh.08:02:37
@vcunat:matrix.orgvcunatThis one is 3.13 on aarch64-darwin: https://hydra.nixos.org/build/31751638408:02:46
@hexa:lossy.networkhexaTwisted, not uvloop, aorry08:03:20
@hexa:lossy.networkhexaCouldn't repro twisted locally08:03:30
@hexa:lossy.networkhexa* uvloop, not twisted, aorry09:19:40
@hexa:lossy.networkhexaimo twisted tests run into timeouts because of ongoing high cpu load on the darwin boxes09:33:23
@hexa:lossy.networkhexabuilt py313/314 twisted on aarch64-darrwin and x86_64-darwin09:33:46
@hexa:lossy.networkhexa * built py313/314 twisted on aarch64-darrwin and x86_64-darwin here 09:36:05
@sternenseemann:systemli.orgsterniMerged staging-next → staging15:13:47
@grimmauld:m.grimmauld.deGrimmauld (any/all)look, there is various security-critical updates in the staging cycle. Python updates is like two months old already. I do not think it is in any way responsible to hold back all of that because some builds are apparently flaky on overloaded darwin build boxes.15:26:23

Show newer messages


Back to Room ListRoom Version: 6