| 18 Jun 2024 |
 Gaétan Lepage | In reply to @zimbatm:numtide.com
There is some historical weirdness. For example the Equinix Metal aarch64 runner is hosted by them. True, I was wondering why this was the case. | 09:51:28 |
 Jonas Chevalier | Access control mostly. The nix-community team would need to get access to the Equinix Metal account, that also hosts all of the Hydra builders, and that gives them access to the binary cache key. | 09:54:05 |
 @3650badcop:catgirl.cloud | In reply to @zimbatm:numtide.com
Yes, we should talk more about it because I think the community build boxes are really helping people debug things in nixpkgs. Imagine if you have a failed package on macOS but don't have a macOS box. Or if this is a very large build and you don't have a lot of compute or bandwidth available. let's go! community build boxes are fantastic!!! | 09:54:59 |
| @3650badcop:catgirl.cloud | sorry i get so excited seeing the success of foss projects | 09:55:16 |
| Gaétan Lepage | Having a beefy >24C/48T x86_64 builder would be the absolute dream. I personnaly fall back to my personal systems to build "heavy" packages (pytorch, JAX, their CUDA variants...) | 09:57:13 |
| Jonas Chevalier | In reply to @zimbatm:numtide.com
Access control mostly. The nix-community team would need to get access to the Equinix Metal account, that also hosts all of the Hydra builders, and that gives them access to the binary cache key. Actually correction: the real issue is that the aarch64 Equinix machine is also running ofborg, that is managed by the NixOS infra team. The mixed usage is actually what makes things complicated. | 10:05:31 |
| Jonas Chevalier | I would also love to see MIPS and other less common architectures in the mix | 10:06:36 |
| Jonas Chevalier | With 2k EUR we could also buy real hardware, and put it in a basement or something. | 10:08:12 |
| Jonas Chevalier | On the community boxes side, it would be nice if people could see who is on the machine, so you don't step over each other. Some sort of whois when you SSH in would already be quite nice. | 10:10:04 |
| Gaétan Lepage | In reply to @zimbatm:numtide.com
On the community boxes side, it would be nice if people could see who is on the machine, so you don't step over each other. Some sort of whois when you SSH in would already be quite nice. Yes that would be nice indeed ! I have done something similar for the GPU cluster in my research team | 10:45:37 |
| Gaétan Lepage | 
Download clipboard.png | 10:45:41 |
 remi-gelinas | Are community build boxes something that's available to the community at large, or how would one go about getting access? | 11:33:50 |
 K900 | 
Download image.png | 11:54:46 |
| K900 | I'll just steal the Darwin builder for the next like couple days lol | 11:55:00 |
| K900 | Nothing to see here just rebuilding everything that depends on mesa | 11:57:46 |
 Mic92 | In reply to @morgrimm:matrix.org
Are community build boxes something that's available to the community at large, or how would one go about getting access? There is a repository: | 14:20:14 |
| Mic92 | In reply to @morgrimm:matrix.org
Are community build boxes something that's available to the community at large, or how would one go about getting access? * https://nix-community.org/community-builder/ | 14:20:23 |
|  redbeardymcgee joined the room. | 15:28:04 |
| Jonas Chevalier | In reply to @glepage:matrix.org
Yes that would be nice indeed ! I have done something similar for the GPU cluster in my research team Oh wow that looks great. How much work is it to set it up? | 18:42:48 |
| Jonas Chevalier | In reply to @morgrimm:matrix.org
Are community build boxes something that's available to the community at large, or how would one go about getting access? yes, we're just asking for a bit of social vetting to minimize the chance of abuse | 18:46:25 |
| Gaétan Lepage | In reply to @zimbatm:numtide.com
Oh wow that looks great. How much work is it to set it up? It's quite hacky and relies on a cron job present on each machine.
Each host publishes its "state" to a local file.
Also, all of their storage is mounted using autofs on the "central node".
The code is open source: https://gitlab.inria.fr/robotlearn/cluster-monitor-2 | 20:08:42 |
| 19 Jun 2024 |
| Jonas Chevalier | thanks. I like the simplicity of it. | 09:24:36 |
| 20 Jun 2024 |
|  nyanbinary 🏳️⚧️ joined the room. | 00:09:48 |
| @3650badcop:catgirl.cloud changed their display name from Ronnie Hounskul (they/them) to Ronnie Hounskul (they/it). | 02:16:12 |
| Gaétan Lepage | Don't know if it's the right place to ask but I noticed a problem with build-bot.
The "rebuild" button doesn't seem to work | 07:39:33 |
 magic_rb | In reply to @glepage:matrix.org
Don't know if it's the right place to ask but I noticed a problem with build-bot.
The "rebuild" button doesn't seem to work I think I know what you mean, if I do, then it's a known issue.
https://github.com/nix-community/buildbot-nix/issues/175
Does that fit? | 08:25:52 |
| magic_rb | I plan to look into it after the 1st of july, currently I'm swamped with university work and studies | 08:26:17 |
|  emily joined the room. | 08:54:05 |
| 21 Jun 2024 |
|  @jade_:matrix.org left the room. | 05:15:54 |
| Gaétan Lepage | Yes, it looks like it is the same issue.
It was actually working before and I don't think to have changed anything on my side.
I will follow this issue, thanks ! | 06:53:15 |
