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

Aberta
#149 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
56/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
testing-qa

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
JavaScript
Estrelas
5
Forks
1
Merge médio
11h 18min
PRs com merge (30d)
66

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TanStack/oracles

Todas as issues de TanStack/oracles

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.