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

You have reached the beginning of time (for this room).


SenderMessageTime
30 Dec 2025
@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
@grimmauld:m.grimmauld.deGrimmauld (any/all)i think we should merge, and let the maintainers of individual packages figure it out.15:26:48
@k900:0upti.meK900I am also leaning towards send it at this point15:34:13
@vcunat:matrix.orgvcunat staging-next merged 🤞 17:48:06
@definfo:matrix.orgcomonad joined the room.17:49:31

Show newer messages


Back to Room ListRoom Version: 6