Conversation
Mirrors duckdb-python's packaging_wheels.yml, narrowed to manylinux_riscv64 and cp312/cp313/cp314 (upstream publishes no free-threaded wheel). Deviations from upstream, all riscv64-driven: - build-frontend `build` instead of `build[uv]`: cibuildwheel's audit step asserts a host uv, which the self-hosted riscv64 runner lacks. - before-build emptied: it installs ccache, which lives in EPEL and manylinux ships no EPEL on riscv64. cmake and ninja still come from scikit-build-core's build requirements; both have riscv64 wheels. - test dependencies listed explicitly instead of exported from uv's lock: pyarrow, polars, adbc-driver-manager and tensorflow have no riscv64 wheels anywhere, and the tests that use them are all behind pytest.importorskip. pandas is pinned to the newest release our registry carries. - upstream's `testsuite: fast` invocation (tests/slow needs network). Verified arch-independently with duckdb 1.5.5 from PyPI and exactly this dependency set: 1853 passed, 146 skipped, 7 xfailed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Builds
duckdb1.5.5 wheels formanylinux_riscv64, mirroring upstream'spackaging_wheels.ymlnarrowed to riscv64 and cp312/cp313/cp314 (upstream publishes no free-threaded wheel,
and its own matrix has none).
Deviations from upstream, all riscv64-driven:
build-frontend: buildinstead ofbuild[uv]— cibuildwheel's audit step asserts ahost
uv, which the self-hosted riscv64 runner does not have.before-buildemptied — upstream installsccache, which only exists in EPEL, andmanylinux explicitly ships no EPEL on riscv64.
cmakeandninjastill come fromscikit-build-core's build requirements; both publish riscv64 wheels on PyPI.
pyarrow,polars,adbc-driver-managerandtensorflowhave no riscv64 wheels anywhere, andevery test that uses them is behind
pytest.importorskip.pandasis pinned to thenewest release our registry carries (pip resolves the highest version across both
indexes, and PyPI's newer ones are x86_64/aarch64 only).
testsuite: fastinvocation (tests/fast);tests/slowandtests/extensionsneed network fixtures.Validated arch-independently before pushing: duckdb 1.5.5 from PyPI plus exactly this
dependency set, staged the way
test-sourcesstages it, gives1853 passed, 146 skipped, 7 xfailed.
Note: the version pin goes through
OVERRIDE_GIT_DESCRIBE, which is upstream's ownset-versionmechanism, so the wheel is plain1.5.5with no.dev/local segment.