-
Notifications
You must be signed in to change notification settings - Fork 11
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
Create an action to push some ARM builds to PyPI #306
Conversation
Mac run failed, this could be related to the old miniconda setup
43aec44
to
aa455ce
Compare
For 1.3.2 we built on x86 Mac (macos-13) but it would be good to have (and test) some ARM wheels as well. We're having trouble building those on older Python versions, but if we upload 3.10 and 3.11 wheels to PyPI that should be somewhat useful. This action is not intended to stick around once py3.8 and 3.9 are deprecated; then we will try to build intel and ARM wheels in the same job.
aa455ce
to
6a2c73a
Compare
This needs to be built against the version-tagged commit or the filenames are wrong for PyPI
workflow_dispatch from non-master doesn't seem to be registering. Instead let's try directly checking-out the target release.
Test Results 41 files + 19 41 suites +19 1h 50m 26s ⏱️ + 1h 17m 39s For more details on these failures, see this check. Results for commit 327d04a. ± Comparison against base commit e85ded5. ♻️ This comment has been updated with latest results. |
- The push trigger allowed a one-time ARM build which has now been manually pushed up to PyPI. (Automatic push didn't work, needed to download artifacts and use twine.) Remove it so the CI doesn't keep rebuilding and failing push. - Now let's confirm that the expected configurations work by testing the PyPI release on both Intel and ARM Mac. (I'm expecting that Intel (macos-13) will work across versions, and ARM (macos-latest) will get the new wheels, while failing to build on Python 3.8, 3.9.)
Troubleshooting test failures here... I *think* the wheels are all built against pre-v2 numpy and so this test is failing due to the ABI change when test runner uses a newer version. In this case we can go ahead and make a new release that builds against the newer Numpy ABI, which requires the min version to be increased to 1.25. One issue will be that Mantid is still on 1.24.
54d08cb
to
5e23cf9
Compare
Conda can't install 1.20 so we weren't getting useful information from the failure.
This branch was used to run some Actions but is not intended for merge. |
No description provided.