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

Abierto
#149 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
56/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript
Área
testing-qa

Línea de trabajo

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.

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

Descripción

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.
Lenguaje dominante
JavaScript
Estrellas
5
Forks
1
Merge medio
11 h 18 min
PR fusionados (30 d)
66

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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

Todos los issues de TanStack/oracles

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.