-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates to Fix Linux ARM32/ARM64 CI #18575
Conversation
looking into using clang-10 which might have even better compatability. don't merge yet till I check later today (few hours) |
this codebase is easily the most unstable thing I have ever worked on. when I crush one bug, 3 more pop up in its place. |
Interesting. We actually never have any issues. Remarkably, both those errors are in third party code. Apparently those projects are not so well maintained for ARM. |
the two that I already mentioned here aren't thirdparty #18575 (comment) also https://github.com/theofficialgman/MuseScore/actions/runs/5547973233/jobs/10130347313#step:7:10320 was fixed upstream at crashpad years ago, you just never pulled it |
next bug to popup https://github.com/theofficialgman/MuseScore/actions/runs/5550053888/jobs/10134787284#step:7:12314 edit: nice, failing on official runs too https://github.com/musescore/MuseScore/actions/runs/5550644575/jobs/10135962814#step:13:2469 |
That |
Its a reported bug with QEMU. I was hoping that bumping from QEMU 7.0.0 to 7.2.0 would fix it but no dice. Only affects arm64 and does not affect the old 4.0.2 build that was able to be built with GCC-7. This is the reported QEMU bug: multiarch/qemu-user-static#172 but thats not the QEMU repo. It should probably be reported upstream to have any chance it being fixed edit: I went ahead and created a bug upstream https://gitlab.com/qemu-project/qemu/-/issues/1763 armhf is not affected and already passes |
@igorkorsukov I believe I have found the original source of the issue with building on the GCC-7 by digging into the log from the CI |
e101631
to
9109237
Compare
@theofficialgman To support cpp11/14, we need to abandon |
333b7cc
to
cc67263
Compare
78f6a78
to
4249942
Compare
Sorry this is taking so long... I was running into issues on armhf and could not diagnose them. I finally determined it is a bug in https://archlinuxarm.org/forum/viewtopic.php?t=16337 What a pain... guess we will be building wget from source on armhf unless Ubuntu fixes the bug promptly which I have just filed https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2043636 |
63c6210
to
d8668a2
Compare
e249b39
to
8f9b286
Compare
… true even though we are not cross compiling we want some flaky tests disabled that hang QEMU
8f9b286
to
cf4bc74
Compare
@igorkorsukov Sorry this took so long. This PR is ready for merge. Refer to the top initial comment for details. edit: |
I wonder whether it'd make sense to also build for arm on PRs (like this) |
Thanks so much for your perseverance with this one, @theofficialgman ! @Jojo-Schmitz I don't think adding this to PR builds is a viable option since these builds take more than 3 hours to complete (because everything needs to be emulated because GitHub has no ARM Linux CI). But it will give nightly builds, if I'm not mistaken. |
Excellent news, this should be great for the Chromebook world! Thanks, @theofficialgman and all who helped make this possible. Now, if someone hadn't stolen the tablet I had been using, I'd be able to help test... |
And it seems to work flawlessly in my virtual arm64 Ubuntu on M1 Mac! That's also very nice! |
@RomanPudashkin any chance you could add the releases from the actions https://github.com/musescore/MuseScore/actions/runs/6980300818 to the https://github.com/musescore/MuseScore/releases/tag/v4.2.0-beta release page (as well as future releases)? I saw you ran both the linux actions and the linux arm actions but the linux arm appimages were not published I think putting it in the official releases will bring a larger audience |
Same request for the Windows PortableApps, see #15876 |
This resolves various issues with the ARM32/ARM64 CI. It switches the CI to building on Focal (like is done for x86_64 linux in the CI). Building on bionic is not possible currently due to this error -> #18516
fixes: #18353