Gap CLI: a nondeterministic test's no-progress verdict kills, and a copy run alone has no idle detection

Ouverte
#149 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
56/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
javascript
Domaine
testing-qa

Piste de recherche

Start with classify.mjs (outcomeOf and cutOf) and check.mjs (countOnly, runUnit, and captureLines) to trace the two reported cases. Then inspect the existing constructed-history tests and add coverage for a nondeterministic idle copy and a batch error followed by a hanging copy. Done means the model and runtime agree on the nondeterministic verdict, and runUnit applies whole-row capture checks and idle detection.

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

Description

Two cases that the merge-gate review of #99 found (L1 and L3). #99 records both in its Limits with this issue as their owner.

1. A nondeterministic test's no-progress verdict kills (L1)

  • A test whose observations differ between the two unmutated runs is nondeterministic. Its ordinary failures judge nothing (classify.mjs outcomeOf, the nondeterministic.has check).
  • A built-in verdict skips that filter: outcomeOf adds each builtIn verdict of a cut copy without it.
  • #99 closes the spin half: a spin kills only when the test is in baseline.work (check.mjs countOnly), and that set leaves out every nondeterministic test.
  • The no-progress half stays open: a copy of a nondeterministic test that goes idle is killed by no progress.
  • The classify oracle's model makes the same prediction (cutOf gives a flaky test's runIdle the law), so it does not see the case.
  • What would close it: the model judges a nondeterministic test's built-in verdict as it judges the test's ordinary failures, and outcomeOf filters builtIn verdicts by their key. The cut rows already carry the key.

2. A copy run alone has no idle detection, and its spin row has no whole-row guard (L3)

  • A batch whose run reports an error outside any test reruns each copy alone (unitsBatch, then runAlone, then unit, then runUnit).
  • runUnit gives its state no idleMs, so a copy that hangs there runs to its backstop: a gap where R50 owes a no progress kill.
  • runUnit's spinRow splits the raw capture text and parses the spin line. It does not use captureLines' whole-row guard, which runner law L1 requires.
  • Reach is low: the path is entered only after a batch completes with an unattributed error.
  • What would close it: runUnit reads its cut rows through captureLines with partial: true, and it cuts an idle row as the batch watchdog does. Add a constructed history whose batch reports an error outside any test beside a hanging copy.
Langage dominant
JavaScript
Étoiles
5
Forks
1
Merge moyen
11 h 18 min
PR mergées (30 j)
66

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

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 TanStack/oracles

Toutes les issues de TanStack/oracles

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

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