| 5 Jan 2025 |
@infinisil:matrix.org | I've heard that you need something from the evals, but I can't see what, because afaik ofborg never built anything other than what commit messages implied (and from comment commands) | 20:07:04 |
emily | (FWIW it was also trying to rebuild nixos/foo which sparked this discussion because I was under the misapprehension(?) that eval somehow factored into what old ofborg decided to build) | 20:10:36 |
@infinisil:matrix.org | Janne HeΓ: Here's how to get to the workflow run from a PR number, assuming that's what you need:
prHead=$(gh api /repos/NixOS/nixpkgs/pulls/371217 --jq .head.sha)
gh api --method GET /repos/NixOS/nixpkgs/actions/workflows/eval.yml/runs -f head_sha="$prHead" -f event=pull_request_target --jq '.workflow_runs | sort_by(.run_started_at) | .[-1]'
| 20:14:12 |
@infinisil:matrix.org | From there you can then use the artifacts API | 20:14:36 |
| collares joined the room. | 22:15:37 |
| 6 Jan 2025 |
| andre4ik3 joined the room. | 14:00:43 |
adamcstephens | Is ofborg building anything? Or just reporting a status message for things it would build? | 21:21:09 |
emily | I think it's theoretically building on x86_64-linux | 21:28:36 |
| 7 Jan 2025 |
7c6f434c | I think have not seen any build reports posted by ofBorg in 2025. | 11:01:27 |
emily | that matches my experience, but I think it's meant to be building? | 11:09:08 |
emily | there's builder hardware that I understand has been hooked up | 11:09:17 |
| 8 Jan 2025 |
Ainz Ooal Gown | + opening a log page shows nginx default page | 01:03:58 |
| 9 Jan 2025 |
andre4ik3 | And https://ofborg.org is down (times out) completely :/ itβs been like this for 3 days. Maybe the switch to GitHub Actions is happening already? π | 03:35:50 |
hexa | still points to the old core.ofborg.org machine | 12:56:58 |
hexa | but the homepage of ofborg is not really relevant for it to be working | 12:57:34 |
| 10 Jan 2025 |
Simon Hauser | I deployed the ofborg-logviewer 2 days ago so that should be working again and the builds are also stable for the past few days now | 16:11:18 |
| 13 Jan 2025 |
hexa | are there plans for aarch64-linux/darwin builders? | 23:27:05 |
| 14 Jan 2025 |
| leona joined the room. | 07:13:00 |
Simon Hauser | 4 aarch64-linux builders for now are deployed. sponsored by helsinki systems. darwin builder are planned | 17:26:04 |
| Winter joined the room. | 20:57:38 |
| 15 Jan 2025 |
cole-h | Hey there, been out of the loop for a bit. Are we still using the hosted CloudAMQP rabbitmq instance? | 17:16:03 |
Simon Hauser | In reply to @cole-h:matrix.org Hey there, been out of the loop for a bit. Are we still using the hosted CloudAMQP rabbitmq instance? No we arent using it anymore and it can be cancelled. Although @janne.hess:helsinki-systems.de and i were talking about maybe copying over the content of the old queues. Not sure though if that is actually necessary. | 17:40:06 |
cole-h | In reply to @simon.hauser:helsinki-systems.de No we arent using it anymore and it can be cancelled. Although @janne.hess:helsinki-systems.de and i were talking about maybe copying over the content of the old queues. Not sure though if that is actually necessary. OK, great! If you could decide if you wanna do that (or not) before 29 Jan 2025, I'd appreciate it (so I can cancel it and only be charged one more time π)! | 17:55:54 |
Simon Hauser | Sounds good π | 18:02:16 |
cole-h | (I'll check in around the 24th ish, but if I don't hear anything will plan on removing my payment info) | 18:07:05 |
| 16 Jan 2025 |
cole-h | Heh, I just got an email from CloudAMQP about sponsoring the instance if we "don't want to self host". I don't have a preference either way. Cc @simon.hauser:helsinki-systems.de | 17:38:55 |
| 17 Jan 2025 |
Simon Hauser | hmm, we dont really need to anymore. the rabbitmq is already selfhosted on the core01 VM. so using a cloud hosted one doesnt give us any benefits, just the downside to do the migration back to the cloud hosted one π
| 09:06:29 |
Janne HeΓ | In reply to @simon.hauser:helsinki-systems.de hmm, we dont really need to anymore. the rabbitmq is already selfhosted on the core01 VM. so using a cloud hosted one doesnt give us any benefits, just the downside to do the migration back to the cloud hosted one π
Yes, I agree with that. The load is completely bearable | 09:19:49 |
cole-h | (I responded thanking them for the offer, and that we will be sticking with self-hosting for now) | 16:53:56 |
| 21 Jan 2025 |
hexa | what is the current capacity like? | 03:52:34 |