| 4 Jan 2025 |
 emily | did you say you might be able to make AArch64 happen? I think a replacement Ampere box would definitely be the most helpful thing for contributors right now | 00:39:54 |
| emily | one because 80 cores is just really convenient for testing out very large builds (I preferred it over the x86 box for this reason), but also because few people have aarch64-linux hardware powerful enough to do substantial builds at all | 00:40:22 |
| emily | we're already seeing e.g. not being able to test the Firefox build on AArch64 because the community builder is gone | 00:40:38 |
| emily | that's quite painful as aarch64-linux is our second best supported platform after x86_64-linux currently | 00:40:54 |
 liberodark | It's actually in my pipeline.
But these are very expensive servers. | 00:41:02 |
| emily | (and increasingly commonly deployed in the cloud etc.) | 00:41:06 |
| emily | yeah :( | 00:41:08 |
| liberodark | Unfortunately I also do with the means I have at my disposal.
I think that to help on this I need a little time to negotiate this point.
I have noted that this was important for you.
But I try to respond to the needs 1 by 1.
The first being equinix. | 00:42:53 |
| emily | FWIW Equinix also provided the community/ofborg AArch64 builders, so I think we currently have no plan for aarch64-linux pre-merge CI too | 00:43:53 |
| emily | but yeah that's the hardest thing to solve of course | 00:43:59 |
| liberodark | Indeed, it was also indicated to me. | 00:44:58 |
| liberodark | And I agree with you that this is not easy to resolve but not impossible. I have some ideas for this. | 00:45:41 |
 zowoq | Upgrading the x86 build box to an epyc 9454p would be nice. | 00:49:03 |
| emily | I'm always in favour of more cores :) | 00:49:18 |
| emily | but I also like testing on aarch64-linux because ~everything already gets built on x86_64-linux during development | 00:49:33 |
| zowoq | Where would this machine be located? Who covers the hosting cost? | 01:05:57 |
