-
Notifications
You must be signed in to change notification settings - Fork 164
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
Use native aarch64 GitHub Action workers #1371
Use native aarch64 GitHub Action workers #1371
Conversation
Test run: https://github.com/IvanIsCoding/rustworkx/actions/runs/12943314687 edit: there are still some warnings like
Most likely we should make the aarch64 steps now wait with the other steps to build and publish |
Pull Request Test Coverage Report for Build 13103659085Details
💛 - Coveralls |
Hmm, that makes me think we have a configuration issue that's explicitly setting the image for aarch64 to x86_64. But that's a bit odd, because I think we only set an image explicitly on x86_64. |
This will go away when I refactor this PR. Right now, the aarch64 build is faster than the default build because i686 spends a lot of time compiling NumPy. So there could be a window of time where there could be no source/pre-compiled wheels for new platforms which is chaos. I will merge |
Simplified test build is running: https://github.com/IvanIsCoding/rustworkx/actions/runs/12971477288 I think we'll be able to just add aarch64 to the OS matrix. That would simplify our setup quite a lot edit: the wheels got built, this is very convenient! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This lgtm, but do you want to promote it to tier 1 and add a test job to our ci test matrix?
Let's merge this first because the release is kind of broken right now. I will defer the tiers for later, but I think we need to some cleanups:
edit: I am tracking the work in #1378 |
Fwiw in qiskit 2.0 we're dropping all 32 bit platform support. I'm not sure we need to necessarily follow what qiskit does here. We can check the download statistics for different platforms and make the call based on that. |
I think that is fair. Let’s check download statistics. My main concern is 32-bit builds breaking the build because of NumPy not compiling. Maybe we could downgrade i686/win32 to Tier 4 |
@Mergifyio backport stable/0.16 |
✅ Backports have been created
|
* Use native aarch64 GitHub Action works * Simplify release structure (cherry picked from commit f2f4542)
Closes #1367
In hindsight we should have used this before the release as the QEMU jobs are really unstable. I might need to backport this to the 0.16 branch and trigger a workflow again.
This is a copy of Qiskit/qiskit#13682. I will test it in my branch and check it works.