| 5 Jan 2025 |
hexa | I don't want to have to deal with that | 01:42:07 |
emily | well, I was thinking it makes more sense to use one machine for both ofborg and community builds (since it was like that before, and the machines are so huge) | 01:43:21 |
emily | it seems like nix-community doesn't have the funding though sadly | 01:43:29 |
Jonas Chevalier | done! | 09:13:11 |
Jonas Chevalier | the refresh might take a while, the TTL was set to 10800 | 09:13:32 |
| @5sqrgsrdwk:matrix.org joined the room. | 11:53:24 |
| @5sqrgsrdwk:matrix.org left the room. | 11:55:05 |
emily | more fun package names :) | 15:22:26 |
emily |  Download image.png | 15:22:32 |
| Ainz Ooal Gown joined the room. | 19:30:52 |
@infinisil:matrix.org | Janne Heß: We never really communicated much around that, but what's exactly the issue with ofborg and evals right now? | 20:06:01 |
@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 |
@adam:robins.wtf | 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 |