!sBfrWMVsLoSyFTCkNv:nixos.org

OfBorg

172 Members
Number of builds and evals in queue: https://nix.ci/prometheus/graph?g0.expr=ofborg_queue_evaluator_waiting&g0.tab=1&g0.stacked=0&g0.show_exemplars=0&g0.range_input=2h&g1.expr=ofborg_queue_builder_waiting%7Barch!~%22.*-lowprior%22%7D&g1.tab=1&g1.stacked=0&g1.show_exemplars=0&g1.range_input=1w64 Servers

Load older messages


SenderMessageTime
26 Dec 2024
@phaer:matrix.orgphaer changed their display name from phaer to phaer (8650 at 38c3).17:42:38
27 Dec 2024
@raitobezarius:matrix.orgraitobezarius changed their display name from raitobezarius to raitobezarius (DECT: 3538 / EPVPN 2681).07:31:46
@janne.hess:helsinki-systems.deJanne HeßI think I am pretty close to completion. I do need access to the current macos hardware (and maybe some rough instructions on how to reconfigure the builder daemon??) and I'd like to reuse the equinix builders until the end of the year so I'd need access to these as well11:36:53
@dimitarnestorov:matrix.orgDimitar set a profile picture.11:41:12
@dimitarnestorov:matrix.orgDimitar changed their display name from dimitarnestorov to Dimitar.11:42:15
@pinpox:matrix.orgpinpox [DECT: 7479] changed their display name from pinpox to pinpox [DECT: 7170].15:23:53
29 Dec 2024
@hexa:lossy.networkhexa Janne Heß: your ssh key? 15:35:08
@janne.hess:helsinki-systems.deJanne Heß ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIM35Bq87SBWrEcoDqrZFOXyAmV/PJrSSu3hl3TdVvo4C janne 15:35:41
@hexa:lossy.networkhexahm, trying to grok the deployment real quick15:39:56
@hexa:lossy.networkhexaok, so morph15:40:48
@hexa:lossy.networkhexaall done16:25:43
@janne.hess:helsinki-systems.deJanne Heßimage.png
Download image.png
20:05:25
@janne.hess:helsinki-systems.deJanne Heßgetting there20:05:27
@emilazy:matrix.orgemilyI'm about a month out of date on plans – is ofborg still going to be responsible for evaluation or is that moving permanently to the GHA?20:25:56
@emilazy:matrix.orgemily(and did the "do actual builds on GHA" plan die?)20:26:02
@janne.hess:helsinki-systems.deJanne HeßI honestly don't know myself tbh20:26:19
@emilazy:matrix.orgemilyfair enough :)20:26:31
@janne.hess:helsinki-systems.deJanne HeßI'm trying to preserve as much as I can from the current way it is (but dropping some GHA-replaced things like the rebuild counters). It's currently in a rough condition but it somewhat works. We still need to eval because the GH API is the absolute worst (at least until someone came up with a better solution)20:27:11
@emilazy:matrix.orgemilyGHA eval is faster than ofborg ever was to a shocking degree (to the point where I wonder how ofborg eval latency ever managed to get bad)20:27:22
@janne.hess:helsinki-systems.deJanne HeßDon't worry, I stole that code to be able to get cheaper machines ;)20:27:43
@janne.hess:helsinki-systems.deJanne Heßevals with ~13-14GB of RAM now20:28:00
@emilazy:matrix.orgemilyyay20:28:08
@emilazy:matrix.orgemily

We still need to eval because the GH API is the absolute worst

as in it's hard to get the eval output from the GHA checks?

20:28:12
@janne.hess:helsinki-systems.deJanne HeßNo, it's actually very easy. I get the event that some GHA check completed and it even tells me on what commit it ran. What it doesn't tell me is the PR this commit belongs to. I asked someone from the merge bot team and they basically told me "listen for push events which contain both the commit hash and the PR and store that somwhere". which isn't really possible since ofborg has no DB20:29:25
@emilazy:matrix.orgemily🥴20:29:43
@emilazy:matrix.orgemilylovely20:29:45
@janne.hess:helsinki-systems.deJanne HeßYeah, huge fun20:29:52
@emilazy:matrix.orgemilyperhaps it could be inverted, though? the GHA could notify ofborg.20:29:58
@emilazy:matrix.orgemilyno passive scanning20:30:08
@janne.hess:helsinki-systems.deJanne HeßSounds like an interesting idea, yeah20:30:26

Show newer messages


Back to Room ListRoom Version: 6