Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
meta: return to v5 of
flatpak-builder workflow
For now return to the version 5 of `flatpak-builder` workflow, until aarch64 job long execution time will be resolved. Signed-off-by: tfuxu <73042332+tfuxu@users.noreply.github.com>
- Loading branch information
6579c69There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We haven't tested the second build after push, there were two builds, one here and one in
shell-themingbranch, which of course uses it's own cache6579c69There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In fact, there were long builds even with older flatpak-builder workflow
https://github.com/GradienceTeam/Gradience/actions/runs/4203630666
6579c69There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was investigating this issue, it is due to GitHub actions which seem to provide runners for x86_64 architecture only but Flatpak builder has support for other architectures and it achieves it using QEMU, I would suggest either removing aarch64 from the workflow as it isn't supported officially here https://github.com/actions/runner-images or I would suggest not bumping flatpak builder version until GitHub actions add official support for ARM runners (Ref: actions/runner-images#5631). (Note: I am looking for alternative solutions for aarch builds so the suggestions made in this comment isn't final)