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

オープン
#149 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
56/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
javascript
領域
testing-qa

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
JavaScript
スター
5
フォーク
1
平均マージ
11時間 18分
マージ済み PR(30日)
66

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

TanStack/oracles のほかの issue

TanStack/oracles の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。