GH-1305: [CI] Drop x86_64 macOS from JNI builds - #1306
Merged
Merged
Conversation
Homebrew treats x86_64 macOS as a tier 3 configuration and rarely builds bottles for it, which keeps breaking the JNI macos-15-intel x86_64 job formula by formula. Remove x86_64 macOS from the RC and test workflows, along with the Homebrew workarounds that only existed for those runners. Release JARs no longer bundle x86_64 macOS .dylib files.
jbonofre
requested review from
kou,
laurentgo,
lidavidm and
wgtmac
as code owners
September 21, 2026 04:58
lidavidm
approved these changes
Sep 21, 2026
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
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.
Rationale for this change
Homebrew treats x86_64 macOS as a tier 3 configuration and rarely builds bottles for it.
brew bundledoesn't build from source, so theJNI macos-15-intel x86_64job in the RC workflow aborts inInstall dependencieswithno bottle available!before anything is compiled.We've been patching this formula by formula:
aws-sdk-cppand gRPC.Any new dependency added to
apache/arrow'scpp/Brewfilecan break the job again the same way, and nightly RC runs go red onmainwhen it does. We can't keep this job green on a configuration Homebrew doesn't support.#1269 noted that dropping the
macos-15-intelentry needed its own discussion because it's user-facing. #1305 is that discussion.What changes are included in this PR?
rc.yml:macos-15-intel/x86_64entry from thejni-macosmatrix.binariesno longer extractsjni-macos-x86_64.tar.gznor asserts the fourjni/*/x86_64/*.dylibfiles./usr/localpython@XXX --overwriteconflict loop. Its comment already said it could go once we droppedmacos-15-intel, sincemacos-14and later on arm64 use/opt/homebrew.brew updateis kept.pkg-configuninstall from itsif [ "$(uname -m)" = "arm64" ]guard, which is now always true.HOMEBREW_BUNDLE_BREW_SKIPcomment. The skip list itself is unchanged:aws-sdk-cppand gRPC are still skipped so the bundled static ones are used, and Node.js is still skipped because the JNI build doesn't need it.test.yml:AMD64/macos-15-intelentry from themacostest matrix, leavingAArch64onmacos-latest.ci/scripts/jni_macos_build.shis untouched, so building the JNI libraries locally on an Intel Mac still works.Are these changes tested?
Yes, by CI. The remaining
JNI macos-14 aarch_64job exercises the changedInstall dependenciesstep, andbinariesexercises the changed artifact extraction and verification.Are there any user-facing changes?
Yes. Release JARs no longer bundle x86_64 macOS
.dylibfiles forarrow_cdata_jni,arrow_dataset_jni,arrow_orc_jniandgandiva_jni. Intel Mac users of those modules will need to build the JNI libraries themselves. aarch64 macOS, x86_64 and aarch64 Linux, and x86_64 Windows are unaffected.Closes #1305.