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

Ouverte
#2,471 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
bash, c, shell
Domaine
testing, tooling

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
C
Étoiles
3
Forks
7
Merge moyen
3 h 28 min
PR mergées (30 j)
270

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de InauguralSystems/EigenScript

Toutes les issues de InauguralSystems/EigenScript

Issues similaires

Plus d'issues C

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.