Closed jeremyd2019 closed 2 years ago
we could just add matrix.name
true, but then all the runners on x64 couldn't share the cache.
I'm wondering, is there a problem with x64/aarch64 sharing the cache? The wheels should all contain their arch in the filename, and the slight duplication shouldn't hurt much..
Doesn't hurt much, no, just downloads wheels it won't use, and then downloads the ones it does want.
Currently the actions/cache action is https://github.com/msys2/msys2-autobuild/blob/de1083d03e6ee7f310ba8a2a29a60ea27b6f5978/.github/workflows/build.yml#L89-L94
If actions/runner#1185 were implemented, I would change this to
${{ runner.os }}-${{ runner.arch }}-pip-
. I don't know that it's worth adding yet anotherstartsWith(matrix.name, 'clangarm')
for it though, because the self-hosted runner already still has the pip cache (and in fact the per-user python modules) between runs.