Build/test/distribute linux_amd64_musl core extensions #15607
Merged
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.
Connected to #15429, adding the
_musltargets to duckdb/duckdb and duckdb/extension-ci-tools#122, adding the dockerfile for building them.After this PR extensions are built, tested and distributed for an extra platform:
linux_amd64_musl.Core extensions that are not currently blocked by build-time issues are:
arrow,icebergandmysql-scanner.jemallochad also some problem building, so I removed it for now, but that should not be visible to users.There are at the moment 4 tests that fail on the musl build, I have not investigated yet why, possibly we are relying on some undefined behaviour in the libc (
muslmight do different choices fromglibcin some areas).Given the vast majory of other tests and extensions tests looks to be working, I would consider the platform as viable BUT experimental.
This also comes with the fact that this is basically untested in the wild (= by actual users).
Unconnected, but likely to generate conflicts, by I changed the names of the repositories to align to the new
duckdb-*scheme.