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

ALCF CI bridge holds a GitHub Actions runner for the whole Aurora pipeline

Aperta
  • Qualcosa non va?
#663 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, gitlab, julia
Ambito
ci-cd, devops

Direzione di ricerca

Start by reading .github/workflows/alcf.yml and the existing log-fetching step, then compare the push-model examples linked in the issue. The proposal spans GitHub Actions and GitLab CI, including dispatch authentication, status reporting, and cancellation behavior. Done means the bridge exits promptly, completion reports the matching pipeline result, and the final status and logs remain visible; the open design questions need resolution first.

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

Descrizione

The ALCF bridge (.github/workflows/alcf.yml) keeps an ubuntu-latest runner alive for the entire Aurora pipeline: after triggering the mirror sync it polls GitLab every 30 s for the pipeline to appear (up to 40 min), then every 60 s until it finishes, with a 330 min timeout to cover the PBS queue wait. Since 2026-09-07 that was 81 jobs and ~3,500 runner-minutes, median 27 min per job, and at least one hit the timeout.

Minutes are free for public repos, but:

  • JuliaGPU is on the free org plan, so every sleeping bridge job holds one of the 20 concurrent job slots shared by all JuliaGPU repositories;
  • Aurora queue time counts against a GitHub Actions timeout, so a busy queue turns into a red check;
  • adopting "the newest pipeline for this SHA" is fragile, which is what needed the re-run workaround in #648.
How others do it

CUDA.jl's benchmark workflow used to wait on Buildkite the same way, and switched to a push model (JuliaGPU/CUDA.jl@7934bfd7): the last Buildkite step calls POST /repos/JuliaGPU/CUDA.jl/dispatches with a benchmarks_complete event, and Benchmark.yml runs on: repository_dispatch, only once results exist. Oceananigans does the same (pipeline-benchmarks.yml). AMDGPU.jl and Metal.jl still poll Buildkite from their Benchmark.yml (via EnricoMi/download-buildkite-artifact-action), and Metal already ran into Buildkite's API rate limit doing so.

Proposal
  1. Keep the trigger side in GitHub Actions (mirror sync, label-gated fork push, fresh pipeline via trigger token on re-run), but have it exit right away after posting a pending commit status on the head SHA, linking to the GitLab pipeline.
  2. Add a final GitLab job (when: always, on the login-node shell runner) that sends a repository_dispatch (e.g. alcf_complete, with pipeline id, SHA and status), using a fine-grained PAT scoped to oneAPI.jl stored as a masked GitLab CI/CD variable.
  3. A short workflow on: repository_dispatch fetches the GitLab job logs (as the current log step does, since the instance requires an ALCF login) and sets the final status/check run on that SHA, linking to its own run.

This frees the runner, decouples Aurora queue time from GitHub timeouts, and matches results by pipeline id instead of guessing. Since the token lives on the GitLab side, fork PRs get results too (unlike CUDA.jl, where fork PRs can't decrypt the dispatch token).

Things to sort out:

  • a pipeline that is cancelled (or whose runner dies) never runs the final job, so its status would stay pending; either accept that or add a scheduled sweep;
  • re-running the GitHub check would now mean triggering a new pipeline, close to what #648 already does;
  • whether ALCF allows outbound HTTPS to api.github.com from CI jobs (the codecov upload suggests so) and storing a GitHub PAT in GitLab variables;
  • if the ALCF GitLab is Premium, its built-in GitHub integration can post pipeline statuses natively, though that wouldn't solve log visibility.

cc @michel2323

Lingua principale
Julia
Stelle
217
Fork
37
Merge medio
18h 12m
PR unite (30g)
26

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 JuliaGPU/oneAPI.jl

Tutte le issue di JuliaGPU/oneAPI.jl

Issue simili

Altre issue su Julia

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.