[CI] Drop x86_64 macOS from JNI builds

Abierto
#1,305 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, java, macos, shell
Área
build-system, ci-cd

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Java
Estrellas
95
Forks
154
Merge medio
2 d 16 h
PR fusionados (30 d)
9

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/arrow-java

Todos los issues de apache/arrow-java

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.