[INFRA] Run the Velox x86, ARM and Kafka PR pipelines in contributors' forks
Los mantenedores suelen responder en 3 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, scala, yaml
- Área
- ci-cd, infrastructure
Línea de trabajo
Read #13535 and inspect .github/workflows/velox_backend_x86.yml to understand the draft fork workflow and its pilot runs. The issue leaves open how to support contributors who cannot enable Actions and says the cache fix still needs CI validation. Done means the fork run and PR result reporting work reliably within the stated ASF constraints, with those open cases addressed.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
In the seven days from 2026-10-27 to 2026-11-02, apache/gluten used about 292,000 GitHub Actions runner-minutes (job durations summed from the Actions API, re-runs included). The ASF policy limits a project's average weekly usage to 250,000 minutes, and projects that keep exceeding it lose Actions access until they fix their builds.
| Workflow (event) | Runs | Runner-minutes | Share |
|---|---|---|---|
Velox Backend (x86), pull_request |
165 | 209,502 | 71.8% |
Delta Spark UT (Gluten), pull_request |
57 | 36,876 | 12.6% |
| All other workflows | 45,590 | 15.6% |
All 165 x86 runs and all 57 Delta runs came from fork PRs.
Proposal
Run velox_backend_x86.yml, velox_backend_arm.yml and velox_kafka.yml for fork PRs in the contributor's fork on push, and report the results on the PR, as Spark has done since SPARK-35048. Fork PR runs of the ARM and Kafka pipelines used another 7,560 and 5,928 runner-minutes that week. Runs in a fork count against the fork owner's account, standard runners are free on public repositories, and a public fork gets the same 4-CPU / 16 GB runners as apache/gluten.
#13535 implements this, and its description has the details and the pilot runs. In short, the fork run tests the PR squash-merged onto the current apache/gluten main and restores the native-build ccache that apache/gluten saves on main. A scheduled workflow in apache/gluten then copies the fork run's result into a check on the PR, without pull_request_target, which the ASF disables from November 2026.
In the pilot, the native build took 4 to 5 minutes with a restored ccache and 113 minutes without one. A full run used about 1,200 runner-minutes of the fork's own quota.
What changes for contributors and reviewers
- Authors have to enable Actions in their fork. Of the 47 forks behind the open PRs on 2026-11-04, 39 had Actions runs since 2026-10-01.
- The check shows up on the PR at the next pass of the scheduled workflow, every 5 minutes, and links to the run in the fork. It fails as soon as a job in that run fails. GitHub can delay scheduled runs.
- Reviewers can't rerun a flaky job in someone else's fork. The author has to, or a committer can push the branch to their own fork and link that run on the PR.
- A free account runs at most 20 jobs at a time, which is also the ASF limit for one workflow. An author with several PRs running at once splits those 20 between them.
- Open PRs get no x86, ARM or Kafka run until their branch is rebased onto
mainafter #13535 and pushed again. - A fork run uses the workflow files of the pushed commit, so a CI change on
mainreaches a PR once its branch is merged or rebased onto thatmain. - The trust model doesn't change:
pull_requestalready runs the PR's own copy of the workflow files.
Follow-ups and open questions
- I don't have a good answer yet for authors who can't enable Actions in their fork. One option is a committer-only comment trigger like
/ansi-test. - Fork PRs don't get the "Report test results" check, because runs in a fork don't trigger
test_report.yml'sworkflow_run.update-fork-build-status.jscould publish the fork runs'*-reportartifacts as that check. - Delta Spark UT can move the same way.
- Switch the status script to
apache/infrastructure-actions/fork-cionce apache/infrastructure-actions#1512 and apache/infrastructure-actions#1513 are fixed. - A fork with a name other than
gluten, such asincubator-gluten, builds under a different workspace path. In a probe it got 0 of 272 ccache hits from the upstream stash. #13535 setsCCACHE_BASEDIRin the CI build scripts, and with it a second probe got 259 hits against the 269 entries it had cached. Existing stashes miss once after the merge, until the cache workflow saves new ones. pr_bot.ymlandclickhouse_be_trigger.ymlstill usepull_request_target. Moving them to theworkflow_runpattern on the ASF policy page is a separate change.- This doesn't replace the ANSI test tags discussed in #13263.
I'd like to hear what you think. cc @philo-he @zhztheplayer
Generated-by: Claude Opus 5.5
- Lenguaje dominante
- Scala
- Estrellas
- 1.6k
- Forks
- 679
- Merge medio
- 4 d 16 h
- PR fusionados (30 d)
- 84
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/gluten
-
[CORE] Selecting a cost model the backend has no coster for fails with ClassNotFoundExceptionPosiblemente ocupada @LuciferYang la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 3 días
-
bug unit testing velox backend
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/gluten#13463 · 1 comentario ·
Los mantenedores suelen responder en 3 días
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
Los mantenedores suelen responder en 3 días
-
[VL] madvise(WILLNEED) call fails in MmapFileStream because of wrong calculation of fetching lengthQuizá libre de nuevo Un pull request para esta issue se cerró sin fusionarse. Abiertobug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 3 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 3 días
Todos los issues de apache/gluten
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
rchillyard/TableParser#206 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 2 días
-
? - Needs Triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
NVIDIA/cudf-spark#17063 ·
Los mantenedores suelen responder en 2 días
-
bug 🐞 User issue 🚨
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
valkey-io/valkey-glide#7813 · 2 comentarios ·
Los mantenedores suelen responder en 1 día