Repository navigation
Conversation
a08456f to
f47f9a7
Compare
|
I've added a setup step to account for riscv64 Python, but it seems there are no Pythons available at any version yet in the GitHub manifests - I'll have to look further into it... |
39af252 to
63b31c8
Compare
|
This is blocked on upstream actions/setup-python#1288 right? |
Right. As soon as I have word there I'll update it again. |
|
I've converted this PR to a draft for the moment. |
63b31c8 to
735cbe9
Compare
735cbe9 to
3c4c4bf
Compare
3c4c4bf to
a08adec
Compare
|
Coming back to this finally. I've rebased the branch and simplified the contributions a bit, including using the RISE version of setup-python as @luhenry suggested, since the upstream one won't be ready for a while yet. I've also dropped the musl build for now to reduce the change scope - I can add it back in if desired. The workflows have been updated since the original in ways that mean I can drop some of the extra variables I was previously setting, e.g. Here's the output of
|
a08adec to
ad2ef0f
Compare
You can use |
ad2ef0f to
325ecb9
Compare
Thanks for the reminder, I had forgotten that we can use setup-python directly now (instead of setup-uv or the RISE fork). Bumped the version and reworded the commit. |
|
The lint failure appears to be a timeout/network issue rather than a real problem with the commits... |
setup-python v7.1.0 supports specifying the `mirror` option when using custom Python distributions is needed, e.g. for the riscv64 architecture. Bump the version and set the mirror conditionally. Signed-off-by: Trevor Gamblin <[email protected]>
325ecb9 to
ff5ffdd
Compare
|
I have a dry run triggered on my fork: here The win-arm64 builds seem to be breaking, and the tests are hitting a networking/timeout issue. Everything else either passed or is still in progress (like the riscv64 builds). EDIT: test step failed because pip was too old - 24.1 is the minimum version for riscv64. I've modified the |
Build polars Python modules for riscv64 by using the riscv64gc-unknown-linux-gnu target. Use a RISE labeled native runner for the 'os'. Make sure to upgrade pip in the 'Test wheel' step, since riscv64 isn't supported before version 24.1. See: https://riseproject-dev.github.io/riscv-runner/ Signed-off-by: Trevor Gamblin <[email protected]>
ff5ffdd to
20561b7
Compare

As part of the RISE Project, we are helping to build riscv64 binary wheels for a variety Python modules. Add support for glibc-based builds by using official RISE RISC-V GitHub Actions Runners. Note that they have to be enabled for the project to use them - instructions for doing so are here.
I've triggered a dry-run on my fork - the riscv64 builds look OK, but Windows ones are failing.. I ran
make checkaftermake buildlocally. Here's the end of that output: