Restore NDKv21 for GitHub Actions #4077
Conversation
GitHub updated the versions of NDK installed on the Actions runners breaking the ARM tests. Restore the NDKv21 using the GitHub suggested mitigation, see: actions/runner-images#5595
|
seems like this fix for NDKv21 stopped working. CI currently fails with https://github.com/official-stockfish/Stockfish/runs/7594674615?check_suite_focus=true |
|
"21.4.7075529" is still the last r21 NDK: The GitHUb runner documentation still shows NDK r21: |
I'm testing the proposed mitigation. |
|
any luck with this test of the mitigation? |
|
Should the ARM tests be turned off until the mitigation is applied so not all commits fail? |
|
yes, I would merge such a PR now. |
No. No other working solutions in the GH thread comments the last time that I have checked. |
|
OK, thanks for testing. Means eventually we need to find a better way to do this, but it is not urgent. |
GitHub updated the versions of NDK installed on the Actions runners breaking the ARM tests. Restore the NDKv21 using the GitHub suggested mitigation, see: actions/runner-images#5595 closes official-stockfish/Stockfish#4077 No functional change (cherry picked from commit d54b85b)
|
@vondele the problem is that GitHub removed NDK 21 from all the Ubuntu runners. That was the last version with the compiler able to write the TLS segment with the right alignment (with a static build) for qemu. Our workflow didn't show the missing NDK 21 because GitHub set the ANDROID_NDK_HOME variable (used by us to update the PATH) to the last NDK version, so our workflow kept using the compiler from the last NDK 25. Some references to try to found a solution: |
GitHub updated the versions of NDK installed on the Actions runners
breaking the ARM tests.
Restore the NDKv21 using the GitHub suggested mitigation, see:
actions/runner-images#5595