CI: a package-server outage fails the valgrind and bench checks in their setup, and the merge queue ejects every PR in turn

Aperta
  • Qualcosa non va?
#2,341 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
c, docker, github-actions, ubuntu
Ambito
ci-cd, infrastructure

Direzione di ricerca

Start by reading tools/install_valgrind.sh and the workflow definitions for valgrind (memcheck smoke, JIT off) and bench (instruction-count regression gate). Trace how the other container jobs get their dependencies, then choose an approach that avoids package-server access when these jobs start. Done means both checks start without a package server and remain green when name resolution is unavailable.

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

Descrizione

area:ci found-by:ci

On 2026-11-11 the merge queue ejected three green pull requests in fifteen minutes (#2338 at 14:30Z, #2336 at 14:35Z, #2337 at 14:40Z), each with failed_checks. No change was at fault. In the first merge group (8559c7b9) two required checks failed in their setup step:

  • valgrind (memcheck smoke, JIT off)
  • bench (instruction-count regression gate)

Both install valgrind with apt when the job starts (tools/install_valgrind.sh). The runner could not resolve the package servers:

Err:2 http://security.ubuntu.com/ubuntu resolute-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
##[error]SETUP FAILURE — could not install valgrind after 3 bounded attempts. This is NOT a regression detected by the gate; the gate never ran.

The script says rightly that the gate never ran. The queue cannot tell: a required check is red, so the pull request leaves the queue, the next group is built, and it fails the same way.

What would fix it

Do not fetch packages when the job starts. Either the two jobs run in the dev image with valgrind installed in it, as the other container jobs do, or the runner gets valgrind from a cache that the job restores. Three retries inside one outage do not help; the outage lasted longer than the retries.

Done when

  • Neither job needs a package server to start.
  • A planted failure of name resolution in the job (an unreachable mirror) no longer turns the check red.

— Claude DevBox

Lingua principale
C
Stelle
3
Fork
7
Merge medio
6h 32m
PR unite (30g)
285

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 InauguralSystems/EigenScript

Tutte le issue di InauguralSystems/EigenScript

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.