Use aarch64 runner for Flatpak

[darkdragon-001]

This brings down the arm64 Flatpak build time from ~180min to ~20min.

[darkdragon-001]

@barthalion Do you have an idea why the arm64 build fails with Error: Failed to update org.gnome.Sdk: Invalid cross-device link?

[barthalion]

This would typically mean something is trying to hardlink across devices. Not sure how much sense this makes in the context of GitHub Actions.

[barthalion]

Anyway, it seems to have failed with some segfault, probably unrelated to that message.

[darkdragon-001]

The arm64 build now seems to work with the image from flathub-infra 😄

[nanu-c]

is this still true?

[darkdragon-001]

I would prefer the image from flatpak instead of flathub-infra as it is more general and smaller and we are also using the action from that repository but the maintainer is not very responsive at the moment. So I suggest keeping the comment for future reference.

[barthalion]

~ ❱ docker images | grep gnome-45
ghcr.io/flathub-infra/flatpak-github-actions   gnome-45   0cd259c4f7c9   26 hours ago   5.45GB
bilelmoussaoui/flatpak-github-actions          gnome-45   e84de63f2fa2   4 days ago     7.55GB

It's actually bigger by 2 GB.

[darkdragon-001]

Interesting, I thought it was the other way round as this was based on the small fedora image. But it looks like it has a lot of inefficiencies like installing Flatpak builder twice (dnf and flatpak) for example.

@barthalion Which GitHub actions and Docker images do you recommend people to use? It is a little bit confusing with the many GitHub organizations and forks...

[barthalion]

The image and action from the flathub-infra org is the one we as in Flathub going to be recommending for the foreseable future.

[darkdragon-001]

@barthalion thanks. Are you just using @master for the version of the GitHub Action? Or pin a commit SHA and update with dependabot?