-
-
Notifications
You must be signed in to change notification settings - Fork 244
feature/build riscv64 wheel #295
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
feature/build riscv64 wheel #295
Conversation
Co-authored by: [email protected];
|
Hi @GrahamDumpleton , could you please help check this PR? |
|
Am not worried about having a test target for that specific architecture as test on enough other platform/architectures. As to the So can you update so |
Other Info Co-authored by: [email protected] Co-authored by: [email protected]
Other Info Co-authored by: [email protected] Co-authored by: [email protected]
|
At a guess, it needs to pin |
|
Ah, mislabelled that last commit as aarch64 and not riscv64. Anyway I remember now why I ditched the aarch64 tests. Because they run under qemu, they take forever to run. So still inclined to not have the riscv64 specific tests. |
|
how about setting the aarch64 and riscv64 tests to be skipped by default, and only tested when there are |
|
I actually removed the action for the aarch64 tests at some point. That was listed under |
|
If you want to check out the build wheels see artefacts on https://github.com/GrahamDumpleton/wrapt/actions/runs/17795323907 |
PyPI recently added support for RISC-V, so we might consider adding support for RISC-V 64.
I used docker+qemu to test the code under riscv64. Below are the CI results:
Build, test and create release packages.
The results are generally well presented.
Since there is no python3.8+riscv64 container on docker hub, I set the riscv64 support to >=3.9
Feel free to contact me anytime, I'll be happy to answer any questions you have.
Other Info
Co-authored by: [email protected];