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

Aperta
#2,471 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
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
bash, c, shell
Ambito
testing, tooling

Direzione di ricerca

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.

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

Descrizione

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

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

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.