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

CI: Intel macOS main suite hits 45-minute limit after the [99i] compile audit

Aperta
  • Qualcosa non va?
#1,261 0 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
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, github-actions, shell
Ambito
ci-cd, operating-systems, testing-qa

Direzione di ricerca

Start with tests/run_all_tests.sh around line 8199 and the macOS workflow in .github/workflows/ci.yml around line 684. Reproduce the main-push lane with [99i] enabled and inspect the Intel logs to attribute the outstanding selftest work. Done means a complete Intel suite followed by the LSP check while retaining the intended platform coverage and fault controls.

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

Descrizione

area:ci kind:gate-defect

Two consecutive main runs on macos-15-intel hit the 45-minute job limit after the [99i] compiler audit prints its successful 585-invocation result. This prevents a complete Intel macOS verdict for the M1 candidate.

Observed runs (UTC, 2026-09-22):

Commit / job [99i] starts Audit reports 585 invocations Cancellation
bb33420, 106623379646 05:26:37 05:35:52 05:53:40
d7f227a, 106880174185 18:50:26 18:59:47 19:13:39

Both check-run annotations explicitly report that the job exceeded 45 minutes. The second job started at 18:28:23, with its main suite starting at 18:29:53. It passed all 15 [99e] SIGUSR1 checks before reaching [99i]. ARM macOS and every other job in that main CI run completed successfully.

At this revision, the suite runs the audit followed by --selftest, capturing selftest output until completion. There is no final [99i] PASS or suite RESULTS line in either Intel log. The available logs do not distinguish a stalled child from cumulative work exceeding the remaining budget; there is no child stack or per-control timing evidence.

The macOS workflow intentionally includes [99i] on main to exercise BSD-userland portability. Its PR lane delegates the audit to Linux, so green PR checks cannot establish completion of this Intel path.

Local serial runs of the candidate passed the complete audit plus selftests: [99i] took 2063.05 seconds in the release suite and 1775.72 seconds in the ASan/UBSan HTTP suite. Whole-suite results were 5350/5350 and 6127/6127 respectively. These are Linux observations, not an Intel macOS diagnosis.

Reproduction: the existing main-push CI lane at either linked commit, with [99i] enabled. No workflow changes, timeout increase or rerun was used in this investigation.

Resolution needs attribution of the outstanding selftest work and a completed Intel suite plus subsequent LSP check while retaining the intended platform coverage and fault controls. This is a distinct observation from #1126's older [99e] stop; it also follows the CI ownership work in #1160.

Lingua principale
C
Stelle
3
Fork
7
Merge medio
3h 56m
PR unite (30g)
102

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.