!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
29 Jul 2021
@hexa:lossy.networkhexathat is the case10:25:53
@vcunat:matrix.orgVladimír ČunátSo the main remaining regression is the PerlMagick problem that seems stuck?10:35:55
@hexa:lossy.networkhexahttps://shells.darmstadt.ccc.de/~hexa/1690057.html10:51:53
@hexa:lossy.networkhexamostly aiohttp10:51:56
@hexa:lossy.networkhexaweirdly enough, if you have restarted failed jobs, they failed again even though aiohttp has succeeded10:53:40
@hexa:lossy.networkhexa * weirdly enough, if you have restarted failed jobs, they failed again with a reference to aiohttp, even though aiohttp has succeeded10:54:26
@vcunat:matrix.orgVladimír ČunátNo, I only did it now.11:00:57
@hexa:lossy.networkhexaah ok, was surprised that home-assistant was still queued, I thought it finished earlier11:08:53
@vcunat:matrix.orgVladimír ČunátIt failed, so I restarted it individually.11:20:43
@vcunat:matrix.orgVladimír ČunátSigh, pytorch gets repeatedly scheduled on wendy again: https://github.com/NixOS/nixos-org-configurations/issues/14612:05:24
@sandro:supersandro.deSandrowendy hit again 😏13:27:04
@hexa:lossy.networkhexawendy 🎉13:46:44
@FRidh:matrix.orgFRidhmass rebuild on master?14:17:10
@FRidh:matrix.orgFRidhoh never mind, it's just because it's a different hydra project14:19:04
@sternenseemann:systemli.orgsterni FRidh: looks like it to me? https://hydra.nixos.org/jobset/nixpkgs/trunk 16:03:06
@sternenseemann:systemli.orgsternithere's also no cache for current master, so seems like it16:03:21
@sternenseemann:systemli.orgsternioh hm seems to be in order mostly16:07:30
@sternenseemann:systemli.orgsterniI screwed up with haskell-updates though since I missed the staging-next merge today16:10:50
@sternenseemann:systemli.orgsterniso that's 20000 builds on master, maybe revert time?16:11:57
30 Jul 2021
@FRidh:matrix.orgFRidh
In reply to @sternenseemann:systemli.org
I screwed up with haskell-updates though since I missed the staging-next merge today
haskell-updates were always merged directly into master. While in principle all larger rebuilds go via staging I can get there are reasons to send it to master though.
06:25:19
@sternenseemann:systemli.orgsterni
In reply to @FRidh:matrix.org
haskell-updates were always merged directly into master. While in principle all larger rebuilds go via staging I can get there are reasons to send it to master though.
we have specifically updated our workflow to minimize the rebuilds by adding all relevant platforms to the haskell-updates jobset and making it a policy to merge master before merging and waiting for any rebuilds, so normally that shouldn't be an issue
09:21:32
@sternenseemann:systemli.orgsternijust forgot to check if there was anything significant on master between merging haskell-updates and the last merging in of master yesterday which was the screw-up09:21:59
@sternenseemann:systemli.orgsternibut seems like the rebuilds finished over night, so not too bad09:22:20
@vcunat:matrix.orgVladimír ČunátMultiple mass-rebuild branches are difficult. I think it's historically the reason why the haskell jobset has such high priority on Hydra (very many scheduling shares).09:22:47
@sternenseemann:systemli.orgsterniI can imagine it was struggling to get build shares with 5000-6000 jobs as it was back then09:29:35
@sternenseemann:systemli.orgsterninowadays a rebuild is like 20000 jobs since we build darwin and aarch64 as well09:29:53
10 Aug 2021
@happysalada:matrix.orghappysalada joined the room.15:27:09
@charlotte:vanpetegem.mechvp joined the room.15:33:58
@asbachb:matrix.orgasbachb joined the room.15:50:40
@jtojnar:matrix.orgJan Tojnar joined the room.17:57:00

Show newer messages


Back to Room ListRoom Version: 6