!sBfrWMVsLoSyFTCkNv:nixos.org

OfBorg

171 Members
Number of builds and evals in queue: <TBD>63 Servers

Load older messages


SenderMessageTime
22 May 2024
@k900:0upti.meK900And that thing already takes forever to build08:17:59
@7c6f434c:nitro.chat7c6f434cI did look at ofBorg to check that the platform-by-platform situation is as expected.08:19:03
@qyliss:fairydust.spaceAlyssa Ross A while a go there was a discussion in this room about raising the timeout on Darwin. On staging PRs it never gets past LLVM, which is part of stdenv, so it's essentially useless — but also, that means that every staging PR is going to take at least an hour of OfBorg time, so I and others suspect that raising the timeout to allow it to finish might actually free up capacity, because it will be able to share LLVM builds. 12:32:05
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.15:25:58
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.15:28:12
@cole-h:matrix.orgcole-h
In reply to @qyliss:fairydust.space
A while a go there was a discussion in this room about raising the timeout on Darwin. On staging PRs it never gets past LLVM, which is part of stdenv, so it's essentially useless — but also, that means that every staging PR is going to take at least an hour of OfBorg time, so I and others suspect that raising the timeout to allow it to finish might actually free up capacity, because it will be able to share LLVM builds.
Right, I remember now... the only problem I have with that is the Darwin queue frequently grows to the hundreds, and I'm afraid that if given e.g. 2 hours (or more) that means the build queue will become even more unmanageable... I dunno, I suppose I'm willing to give it a shot, just let me what you think we should start with (2? 3? 6 hours before timeout?)
22:45:13
23 May 2024
@qyliss:fairydust.spaceAlyssa Rossshouldn't need to be more than 306:42:05
@qyliss:fairydust.spaceAlyssa Rossnot sure if 2 would be enough06:42:08
@hexa:lossy.networkhexaare the builders sharing a cache of any kind?13:01:10
@hexa:lossy.networkhexaor would every individual builder have to build their own llvm13:01:23
@k900:0upti.meK900Even if they share a cache they don't share locks13:01:43
@k900:0upti.meK900So they'll attempt to race13:01:47
@hexa:lossy.networkhexayes, but you can't have it all 🙂 13:04:12
@cole-h:matrix.orgcole-hofborg has a queue, so if one builder picks up the only LLVM build, nobody else can pick it up14:38:40
@cole-h:matrix.orgcole-h
In reply to @qyliss:fairydust.space
shouldn't need to be more than 3
I'll give it a shot later today and we'll see how it goes.
14:39:29
@7c6f434c:nitro.chat7c6f434cIt's not an LLVM build, it's an LLVM-dependent build though14:40:49
@cole-h:matrix.orgcole-hGotcha, I misunderstood the concern14:41:15
@hexa:lossy.networkhexaand caching?18:10:57
@hexa:lossy.networkhexaif one builder has the result, can others reuse it? 😛18:11:03
@cole-h:matrix.orgcole-hNo, no caching between machines at this moment18:11:34
@qyliss:fairydust.spaceAlyssa Rossah, I assumed there would be18:12:48
@qyliss:fairydust.spaceAlyssa Rossthat makes me less confident it would save time 18:12:57
@hexa:lossy.networkhexawondering, does haumea run on darwin?18:13:49
@hexa:lossy.networkhexathat would allow sharing directly from the /nix/store18:14:05
@cole-h:matrix.orgcole-hNo clue what haumea is, so can't comment18:14:38
@hexa:lossy.networkhexaharmonia18:14:48
@hexa:lossy.networkhexasorry 😄 18:14:48
@cole-h:matrix.orgcole-h(Other than it was at one point? the name of the hydra db I think)18:14:56
@hexa:lossy.networkhexahttps://github.com/nix-community/harmonia18:14:59
@hexa:lossy.networkhexayeah, my head wandered a bit18:15:10

Show newer messages


Back to Room ListRoom Version: 6