ci: use pypa/cibuildwheel action directly for riscv64 native runner#482
Merged
Merged
Conversation
The previous approach used a custom run step with pipx to invoke cibuildwheel on the riscv64 native runner. This relied on /opt/python-3.1*/bin paths that no longer exist after the RISE runner image rebuild on 2026-04-22. Using the pypa/cibuildwheel GitHub Action directly handles Python setup on all platforms including riscv64, removing the need for the special- cased step. Signed-off-by: Bruno Verachten <gounthar@gmail.com>
Contributor
Author
|
Thanks for the quick merge! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The riscv64 build step was using a manual
runblock to invokecibuildwheel via pipx, with a glob to find Python under
/opt/python-3.1*/bin. That broke after the RISE riscv64 runner imagewas rebuilt on 2026-04-22. The
/opt/python-3.12paths are gone, theglob finds nothing, PATH falls back to system Python 3.12, and
pip install pipxhits PEP 668 (Ubuntu 24.04 blocks system-levelinstalls without
--break-system-packages).The fix: use the
pypa/cibuildwheelaction directly, same as everyother architecture in this workflow. The action handles Python setup
internally and works fine on
ubuntu-24.04-riscv.I also dropped the
if: matrix.archs != 'riscv64'guard on the Buildwheels step. One unified step now covers everything, which avoids the
two paths slowly diverging over time.
Tested on the RISE native riscv64 runner (
ubuntu-24.04-riscv):https://github.com/gounthar/RapidFuzz/actions/runs/25289792932