!sBfrWMVsLoSyFTCkNv:nixos.org

OfBorg

170 Members
Number of builds and evals in queue: <TBD>62 Servers

Load older messages


SenderMessageTime
20 Feb 2024
@cole-h:matrix.orgcole-hIt's not actually space that's the issue, but inodes, since they run on ext417:01:26
@lily:lily.flowersLily Fosterah17:01:33
@lily:lily.flowersLily Fosterwell. that would do it17:01:36
@lily:lily.flowersLily Foster (i wonder if auto-optimise-store would be reasonable to save on inodes 🤔) 17:02:08
@lily:lily.flowersLily Foster(idk maybe they're already doing that too)17:02:13
@cole-h:matrix.orgcole-hThey used to run on zfs, but when EM refreshed their hardware, we would sometimes get machines that didn't support EFI (this was like 2+ years ago now so I don't remember the exact details, but something something no EFI = no ZFS booting)17:02:29
@janik0:matrix.org@janik0:matrix.orgokay, thank's that explains the error :)17:03:59
22 Feb 2024
@hexa:lossy.networkhexacan we? https://github.com/samueldr/ofborg-viewer/pull/2800:13:11
@hexa:lossy.networkhexaplease?00:13:14
@hexa:lossy.networkhexadark mode!00:13:19
@adam:robins.wtf@adam:robins.wtf > Use nodejs 20 instead of nodejs 6
01:31:02
24 Feb 2024
@sandro:supersandro.deSandro 🐧
In reply to @hexa:lossy.network
can we? https://github.com/samueldr/ofborg-viewer/pull/28
Can we get logs grouped by package? 🥺
14:58:00
@hexa:lossy.networkhexathat is pretty much orthogonal to what you quoted.14:58:38
@sandro:supersandro.deSandro 🐧I mean if someone is working on it, maybe that's the time to implement new features?14:59:36
@hexa:lossy.networkhexathere is no clear maintenance declared on the project14:59:42
@hexa:lossy.networkhexamaybe, maybe not14:59:54
25 Feb 2024
@simonmenke:matrix.orgSimon Menke set a profile picture.15:25:56
28 Feb 2024
@qyliss:fairydust.spaceAlyssa RossCould we have higher darwin timeouts for staging PRs, or something? OfBorg Darwin is basically completely useless on staging PRs, because it can never get past LLVM, which takes >3600 seconds to build.14:17:09
@hexa:lossy.networkhexaI think we're more affected by the sheer lack of build capacity for aarch64-darwin than its timeouts14:19:39
@hexa:lossy.networkhexabut yeah, I've seen it often fail on llvm for … basically anything staging14:20:11
@qyliss:fairydust.spaceAlyssa Rosswell, currently we're wasting a lot of that capacity on LLVM builds that are never going to finish14:20:39
@hexa:lossy.networkhexatrue14:20:46
@qyliss:fairydust.spaceAlyssa Rossso if we can't get more capacity, maybe we should just turn OfBorg Darwin off for staging14:21:03
@qyliss:fairydust.spaceAlyssa Rosssince it's just wasting more than an hour of build time per PR, and is basically guaranteed not to produce any useful result 14:21:31
@adam:robins.wtf@adam:robins.wtfthere was some discussion above about moving to all aarch64 builders and running x86 on those instead, but i don't think any changes were made14:21:32
@adam:robins.wtf@adam:robins.wtf(not that that helps this specific timeout, but potentially it helps overall capacity)14:23:00
@lily:lily.flowersLily Fosteryeah increasing the timeout may help that problem for sure. we could just try it and see14:23:22
@hexa:lossy.networkhexa5x x86_64-linux, 1x aarch64-linux, 2x aarch64-darwin, 3x x86_64-darwin14:23:24
@hexa:lossy.networkhexa *
  • 5x x86_64-linux,
  • 1x aarch64-linux,
  • 2x aarch64-darwin,
  • 3x x86_64-darwin
14:23:46
@hexa:lossy.networkhexa *
  • 5 x86_64-linux,
  • 1 aarch64-linux,
  • 2 aarch64-darwin,
  • 3 x86_64-darwin
14:23:51

Show newer messages


Back to Room ListRoom Version: 6