gates: the precheck self-test's count is pinned twice (registry row and suite section 99zb0); adding a case moves one and reds four hosted jobs

Abierto
#2,471 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
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bash, c, shell
Área
testing, tooling

Línea de trabajo

Read tools/selftests.txt and section [99zb0] in tests/run_all_tests.sh, then inspect how tools/precheck.sh --selftest reports its results and how the self-test driver reads registry entries. Reproduce the mismatch by adding a case and moving only the registry count; also verify a failing case makes the section fail. Check all ten suite lines mentioning self-tests and document any literal counts that remain with their reason.

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

Descripción

area:gates kind:gate-defect needs-triage

tools/precheck.sh --selftest prints precheck-selftest: N/N passed, 0 failed, and that line is pinned by its literal count in two places: the registry row in tools/selftests.txt and the suite's section [99zb0] in tests/run_all_tests.sh (grep -q '^precheck-selftest: 11/11 passed, 0 failed$').

A change that adds a case to the self-test has to move both. The registry row is found by anyone who edits the tool (the registry names the tool's file); the suite's literal is not. On 2026-11-21 a change that added the eleventh case (#2458, in #2464) moved the registry pin and left the suite at 10/10: four hosted jobs went red on that one line, and the local acceptance had run the registry row and not the section. The day before, another count was missed the same way.

The second pin adds no check the first does not make: both run the same command and compare the same line.

Done when

  • Section [99zb0] does not hold a second literal of the count: it takes its expected line from the registry row of tools/precheck.sh (one reader, as the selftest driver reads it), or it asks only what the registry does not (exit code 0, 0 failed, and the count on the line equal to the number of PASS: lines the run printed).
  • Shown red first: with one case added to the self-test and only the registry row moved, the section passes; with a case made to fail, it fails.
  • git grep for the other self-test summaries the suite pins by a literal count (the suite has ten lines that mention a selftest): each is either derived the same way or listed here with the reason it stays.

— Claude DevBox

Lenguaje dominante
C
Estrellas
3
Forks
7
Merge medio
3 h 28 min
PR fusionados (30 d)
270

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.