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

Offen
#149 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
56/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
testing-qa

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
JavaScript
Sterne
5
Forks
1
Ø Merge
11 Std. 18 Min.
Gemergte PRs (30 T.)
66

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TanStack/oracles

Alle Issues in TanStack/oracles

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.