jbonofre opened a new pull request, #1269:
URL: https://github.com/apache/arrow-java/pull/1269
### Rationale for this change
The `JNI macos-15-intel x86_64` job in the RC workflow fails in `Install
dependencies`, before anything is built:
```
##[error]aws-sdk-cpp: no bottle available!
##[error]grpc: no bottle available!
This is a Tier 3 configuration:
https://docs.brew.sh/Support-Tiers#tier-3
`brew bundle` failed! 2 Brewfile dependencies failed to install
```
Homebrew treats x86_64 macOS as a [tier 3
configuration](https://docs.brew.sh/Support-Tiers#tier-3) and rarely publishes
bottles for it. `brew bundle` doesn't build from source, so
`arrow/cpp/Brewfile` can no longer be installed as-is there.
This breaks `main` too, not just PRs, so nightly RC runs are red.
### What changes are included in this PR?
We don't use Homebrew's `aws-sdk-cpp` and gRPC anyway:
* The JNI macOS build uses the `ninja-release-jni-macos` preset, which sets
`ARROW_DEPENDENCY_USE_SHARED=OFF`.
* Homebrew provides only shared libraries for `aws-sdk-cpp` and gRPC.
* So both are uninstalled just after `brew bundle` to ensure the bundled
ones are used.
We skip installing them with `HOMEBREW_BUNDLE_BREW_SKIP` instead of
installing and uninstalling them. This also makes the `macos-14` `aarch_64` job
a bit faster because it no longer installs two formulae it immediately removes.
`brew uninstall aws-sdk-cpp` needs `|| :` now because it's no longer
installed by `brew bundle`. It's still called because it may be pre-installed
on GitHub Actions runner images.
Note that this keeps building the x86_64 macOS shared libraries. Dropping
the `macos-15-intel` entry would remove `.dylib` files for x86_64 macOS from
our release JARs, which needs a separate discussion.
### Are these changes tested?
Yes, by CI. The `JNI macos-15-intel x86_64` and `JNI macos-14 aarch_64` jobs
in this PR exercise the changed step.
### Are there any user-facing changes?
No.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
