!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/113 Servers

Load older messages


SenderMessageTime
28 Dec 2025
@leona:leona.isleonathen I agree08:33:18
@hexa:lossy.networkhexauvloop is stubbornly flaky08:33:34
@hexa:lossy.networkhexabut it just built on hydra on aarch64-darwin08:33:41
@hexa:lossy.networkhexanow it fails on numpy08:33:53
@hexa:lossy.networkhexanumpy is cached08:34:19
@hexa:lossy.networkhexanvm08:34:21
@hexa:lossy.networkhexaok, I'm disabling a test on uvloop09:30:54
@hexa:lossy.networkhexa* ok, I'm disabling a test on uvloop on darwin09:30:57
@hexa:lossy.networkhexanot sure why it appeared cached to me, maybe I got lucky09:31:11
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/47475809:41:09
@grimmauld:m.grimmauld.deGrimmauld (any/all) with c23, some things (e.g. nasm) fail in a creative way: They check whether stdbool.h is available, and include it if so. Which obviously breaks on C23, where bool can't be typedefed. No idea why this didn't break on glibc, i didn't look at that 🤷 19:22:55
29 Dec 2025
@ghpzin:envs.net@ghpzin:envs.net typedefs in stdbool.h are conditional on __STDC_VERSION__ > 201710L
So you can safely include it there.
In musl version they are not.
03:04:01
@ghpzin:envs.net@ghpzin:envs.net typedefs in stdbool.h are conditional on __STDC_VERSION__ > 201710L
So you can safely include it there.
In musl version they are not:
https://git.musl-libc.org/cgit/musl/tree/include/stdbool.h
03:06:02
@ghpzin:envs.net@ghpzin:envs.net true/false in stdbool.h are conditional on __STDC_VERSION__ > 201710L
So you can safely include it.
In musl they are not:
https://git.musl-libc.org/cgit/musl/tree/include/stdbool.h
07:58:27
@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.orgVladimír Čunát The current release-25.05..staging-25.05 will probably never get merged anymore. 14:29:38
@vcunat:matrix.orgVladimír Čunát(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.orgVladimír Čunát 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.orgVladimír Čunát * 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.orgVladimír Čunát

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.orgVladimír Čunát(PRs currently open against staging-next seem to fix at most a couple hundred jobs)07:46:45
@vcunat:matrix.orgVladimír Čunát *

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.orgVladimír ČunátThey'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.orgVladimír ČunátIf they're that much flaky, I consider them as good as always failing.08:00:56

Show newer messages


Back to Room ListRoom Version: 6