Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#1,261 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, github-actions, shell
Área
ci-cd, operating-systems, testing-qa

Línea de trabajo

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.

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

Descripción

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.

Lenguaje dominante
C
Estrellas
3
Forks
7
Merge medio
4 h 15 min
PR fusionados (30 d)
106

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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

Todos los issues de InauguralSystems/EigenScript

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.