Draft: Run CI on ArchLinuxARM #8

WhyNotHugo commented 2022年07月18日 20:49:38 +02:00 (Migrated from gitlab.com)

Often builds fail on ALARM, but work on Manjaro.

Often builds fail on ALARM, but work on Manjaro.

WhyNotHugo commented 2022年07月18日 20:50:47 +02:00 (Migrated from gitlab.com)

Does CI need to be approved or something?

Does CI need to be approved or something?

ohfp commented 2022年07月26日 11:41:33 +02:00 (Migrated from gitlab.com)

Yep. I have to spin up a (paid) instance at https://www.equinix.com/ for the aarch64 builds, so those don't automatically run.

Can you give me some more details why/how builds fail on ALARM? I'm somewhat torn on what to build on: Many people seem to use Manjaro on aarch64 devices, so building it with that in mind seemed reasonable back then, but considering it sometimes seems to lag behind for a week or two with dependencies, that's not optimal as well.
Still, things seem to have worked so far with the resulting binaries for most users, so I'd not want to change it if not for a good reason.

Yep. I have to spin up a (paid) instance at https://www.equinix.com/ for the `aarch64` builds, so those don't automatically run. Can you give me some more details why/how builds fail on ALARM? I'm somewhat torn on what to build on: Many people seem to use Manjaro on `aarch64` devices, so building it with that in mind seemed reasonable back then, but considering it sometimes seems to lag behind for a week or two with dependencies, that's not optimal as well. Still, things seem to have worked so far with the resulting binaries for most users, so I'd not want to change it if not for a good reason.

WhyNotHugo commented 2022年07月31日 16:43:03 +02:00 (Migrated from gitlab.com)

The exact issue building has varied over time, and most of the times I've no idea what's causing it.

Currently, it's:

:: Resolving dependencies...
error: could not find all required packages:
 wasi-libc>=1:0+258+30094b6 (wanted by: librewolf)

So it seems that there's a dependency on a package that's available on x86_64 but hasn't built on aarch64 yet.

Yep. I have to spin up a (paid) instance at https://www.equinix.com/ for the aarch64 builds, so those don't automatically run.

Lemme try and see if I can figure out something better for this. :)

The exact issue building has varied over time, and most of the times I've no idea what's causing it. Currently, it's: ``` :: Resolving dependencies... error: could not find all required packages: wasi-libc>=1:0+258+30094b6 (wanted by: librewolf) ``` So it seems that there's a dependency on a package that's available on x86_64 but hasn't built on aarch64 yet. > Yep. I have to spin up a (paid) instance at https://www.equinix.com/ for the `aarch64` builds, so those don't automatically run. Lemme try and see if I can figure out something better for this. :)

ohfp commented 2022年08月01日 19:11:57 +02:00 (Migrated from gitlab.com)

Luckily, the wasi-packages are any-packages, so you can just use the ones from Arch.
(I've added the version constraints for things to fail early, until ALARM provides the updated ones – otherwise, it'll fail an hour in or so).

I've worked around that issue for the CI builds like this: https://gitlab.com/librewolf-community/browser/arch/-/blob/master/ci.build.sh#L9-17

Luckily, the wasi-packages are `any`-packages, so you can just use the ones from Arch. (I've added the version constraints for things to fail early, until ALARM provides the updated ones – otherwise, it'll fail an hour in or so). I've worked around that issue for the CI builds like this: https://gitlab.com/librewolf-community/browser/arch/-/blob/master/ci.build.sh#L9-17

WhyNotHugo commented 2022年08月02日 20:15:54 +02:00 (Migrated from gitlab.com)

Luckily, the wasi-packages are any-packages, so you can just use the ones from Arch.

Yeah, downstream ALARM seems to rebuild those. I've mentioned that they can just mirror upstream's, but it's fallen on deaf years.

I'll try to set up my own runner somehow and let you know -- I need a builder/runner other aarch64 arch packages anyway.

> Luckily, the wasi-packages are any-packages, so you can just use the ones from Arch. Yeah, downstream ALARM seems to rebuild those. I've mentioned that they can just mirror upstream's, but it's fallen on deaf years. I'll try to set up my own runner somehow and let you know -- I need a builder/runner other aarch64 arch packages anyway.

This pull request is broken due to missing fork information.