Closed jeremyd2019 closed 3 years ago
I have not checked what effect having a clangarm64 build-type in the JOB_META
array would be while clangarm64 is in MANUAL_BUILD_TYPE
.
Using my fork of setup-msys2 is probably a non-starter. I can remove that hunk from the pull request.
yeah.. the rest looks fine to me.
I have to say, I was surprised by how "easy"/non-invasive this was. Nice when it works out that way
cool, it doesn't appear to have tried to fire up a clangarm64 job. 😌
A couple of runs on my self-hosted runner have failed due to a timeout downloading packages in pacman as part of the setup-msys2 action, and for the ones that succeeded uploading the package cache to github's cache service failed with a 503 error (but that didn't fail the workflow)
Workflow improvements to support a self-hosted runner on Windows ARM64. The biggest issue is that the currently released versions of Windows on ARM64 do not support x64 emulation, only x86.
${{ runner.arch }}
instead of seeing what the name starts with.