CI: macOS harness failures and timeouts block dependency PR 1125
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
- 35/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Área
- ci-cd, devops, testing-qa
Línea de trabajo
Start with CI run 34329218345 attempt 2 and the logs for macOS jobs 103459661817 and 103459661756, then inspect the replay selftest, strict differential, and [99e] sections around the cited lines. Compare the extensions job 103459661842 around lines 5242–5247. Done means establishing reproducible causes and validating a fix with a rerun that unblocks PR #1125.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
PR #1125 remains unready: both macOS jobs report shell/test-output portability failures before timing out, while the extensions job reaches its limit during a third variant suite. The dependency diff only updates pinned Docker/Pages action versions.
Read-only follow-up for PR #1125, head 2ce7802ed07138efe0771351173bd95f07c79fbb, CI run 34329218345 attempt 2.
The direct Actions job-log API recovered all three logs. Each job annotation confirms the 30-minute execution limit, but the logs show more than a timeout-only problem.
Observed failures before timeout on both macOS jobs:
- Replay selftest returned 1, with 5/6 controls passing. Its clean-boundary positive returned 0, but the count line contained padded
0 ledgeredinstead of the expected0 ledgered. - Strict differential failed with
line 197: BASHPID: unbound variable. Both the matcher selftest and subsequent run report an untrustworthy section verdict.
These failures do not establish a runtime semantic regression or an action-version cause.
Where the jobs stopped:
- macOS latest, job 103459661817: [99d] passed at 00:00:53Z; [99e] SIGUSR1 observer dump began immediately afterward, with no further suite output until cancellation 00:24:41Z. Log lines 2278–2279 show that interval. Cleanup line 2314 names an orphan
eigenscriptPID 73248. - macOS Intel, job 103459661756: [99d] passed 00:04:07Z; [99e] then remained the last observed section until 00:24:37Z cancellation (lines 2345–2346). Cleanup line 2381 names
eigenscriptPID 88750. Replay/strict errors are visible around lines 2316 and 2331. - Extensions, job 103459661842: http+model and gfx full-suite steps succeeded. The zlib suite began 00:20:18Z and reached [69] Leak Guard immediately after [71] teardown passed. Lines 5242–5247 show the last PASS, section header and cancellation 00:24:23Z. Net suite, LSP/DAP checks and fuzz smoke were skipped.
Times are UTC 2026-09-12. The macOS logs reveal process names/PIDs, not actual child argv or stacks. The extensions log supplies no active child identity. Thus [99e] and [69] are last observed work, not fully attributed hang diagnoses. Extensions also had already consumed most of its shared 30-minute budget before zlib began.
No rerun, workflow change, source change or timeout increase was made in this investigation. Raising the deadline alone is not an established fix: macOS already has hard failures, and its silent [99e] interval differs from the extensions job's cumulative budget. PR #1125 remains unready.
- Lenguaje dominante
- C
- Estrellas
- 3
- Forks
- 7
- Merge medio
- 4 h 5 min
- PR fusionados (30 d)
- 116
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Incluye un Dockerfile o un 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 InauguralSystems/EigenScript
-
area:docs good first issue kind:docs-drift
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
InauguralSystems/EigenScript#1400 ·
Los mantenedores suelen responder en 1 día
-
area:docs good first issue kind:docs-drift
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
InauguralSystems/EigenScript#1396 ·
Los mantenedores suelen responder en 1 día
-
docs/BUILTINS.md: task_spawn row says task_yield/task_join 'land in a later increment'; both existAbiertoarea:docs good first issue kind:docs-drift
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
InauguralSystems/EigenScript#1392 ·
Los mantenedores suelen responder en 1 día
-
area:embed kind:silent-wrong
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
InauguralSystems/EigenScript#1387 ·
Los mantenedores suelen responder en 1 día
-
area:stdlib kind:silent-wrong
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
InauguralSystems/EigenScript#1378 ·
Los mantenedores suelen responder en 1 día
Todos los issues de InauguralSystems/EigenScript
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
trezor/trezor-firmware#7997 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
area/ysql kind/bug priority/medium status/awaiting-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
yugabyte/yugabyte-db#34415 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 78/100
KhronosGroup/OpenCL-Headers#318 ·
-
Build failure: mumbleAbierto0.kind: build failure
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día