Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[CI] Drop x86_64 macOS from JNI builds

Chiusa
#1,305 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, java, macos, shell

Direzione di ricerca

Read rc.yml and test.yml first, focusing on the jni-macos, binaries, and macos matrix entries. Then inspect ci/scripts/jni_macos_build.sh and the Homebrew workaround sections. Done means x86_64 macOS is removed from the specified CI matrices and artifact checks, Intel-only workarounds are removed, and local x86_64 JNI builds remain supported.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the enhancement requested

Homebrew treats x86_64 macOS as a tier 3 configuration and rarely builds bottles for it. This has broken the JNI macos-15-intel x86_64 job in the RC workflow repeatedly, because brew bundle doesn't build from source and aborts with no bottle available! before anything is compiled:

  • #1269 worked around it for aws-sdk-cpp and gRPC.
  • #1270 worked around it for Node.js.

Each of these was a formula-by-formula patch, and any new dependency added to apache/arrow's cpp/Brewfile can break the job again the same way. We can't keep an x86_64 macOS JNI build green on a configuration Homebrew doesn't support.

As noted in #1269, dropping the macos-15-intel entry needs its own discussion because it is user-facing, so this issue is that discussion.

Proposal

Drop x86_64 macOS from CI:

  • rc.yml: remove the macos-15-intel / x86_64 entry from the jni-macos matrix, and stop extracting and verifying jni-macos-x86_64.tar.gz in the binaries job.
  • test.yml: remove the AMD64 / macos-15-intel entry from the macos test matrix.
  • Remove the Homebrew workarounds that only existed for the x86_64 runners (the /usr/local python@XXX --overwrite conflict loop, and the uname -m guard around the pkg-config uninstall).
User-facing impact

Release JARs would no longer bundle x86_64 macOS .dylib files for arrow_cdata_jni, arrow_dataset_jni, arrow_orc_jni and gandiva_jni. Intel Mac users of those modules would need to build the JNI libraries themselves. ci/scripts/jni_macos_build.sh still handles x86_64, so a local Intel build keeps working.

aarch64 macOS, x86_64 and aarch64 Linux, and x86_64 Windows are unaffected.

Component(s)

Java, CI

Lingua principale
Java
Stelle
95
Fork
154
Merge medio
2g 10h
PR unite (30g)
11

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/arrow-java

Tutte le issue di apache/arrow-java

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.