You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to build macOS arm64 wheels for my project on Azure pipelines, but this specific platform is failing (default MacOS and linux are fine) is failing during tests (building is succeeding) with the error:
OK, the solution I have found for now is to skip tests for arm64, so in my azure template in the install wheel and test:
condition: ne(variables['PLAT'], 'arm64'
That produces wheels for macos 11 (As I set the MACOSX_DEPLOYMENT_TARGET to 11.0) which seem to work well.
It would be of course be better to have the tests in place. If I understand correctly, what is happening here is that in my job matrix I have MB_PYTHON_OS_VER set to 10.9, and probably that old python doesn't recognize the wheel for osx 11. I tried to set the MB_PYTHON_OS_VER to 11, but that fails because multibuild is naming the python package to be downloaded incorrectly:
Python download failed! Check python-3.8.10-macosx11.0.pkg exists on the server.
when the package is named python-3.8.10-macos11.0.pkg (not macosx, the x is not needed, see here, so it seems to me that multibuild needs adaptation at that point.
hi
I am trying to build macOS arm64 wheels for my project on Azure pipelines, but this specific platform is failing (default MacOS and linux are fine) is failing during tests (building is succeeding) with the error:
I tried to do something similar as this one, but didn't manage: https://github.com/MacPython/scipy-wheels/pull/150/files
What am I doing wrong?
Here is my azure yml: https://github.com/ofajardo/pyreadr_wheels4/blob/master/azure-pipelines.yml
and here the azure pipelines failing: https://dev.azure.com/ofajardo/pyreadr_wheels4/_build/results?buildId=105&view=logs&j=edc54a0e-92d1-574b-433e-80fdfaa23be3&t=d0e4c54a-7f31-5215-670d-55d58cc754a5&l=51
thanks in advance for the help!
The text was updated successfully, but these errors were encountered: