Gap e2e: load-time reach of an owner file with no plan test is not modeled (exposed by per-law blocking)

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

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript

調査の方向性

Start with src/sut.ts at D_OBJ:30 and the gap report replay in packages/oracles; compare the reported not-distinguished result with the two cited CI counterexamples. Read how the model and runner handle module-load reach, especially with isolate: false, then decide whether to model that rule or document the limit until the CLI records load reach per file. Done means the maintainer’s chosen behavior is captured and the counterexample is resolved or recorded as a stated limit.

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

説明

The end-to-end gap oracle on PR #176 (head 7f8e8104) found a counterexample. Its model cannot decide it, so this issue brings it to the maintainer.

  • Unit: random seed: a declaration fault: brokenOwner, seed 101
  • Difference: src/sut.ts:D_OBJ:30:field-drop#0: not-distinguished, owed indeterminate

Replay (from packages/oracles):

ORACLE_SEED=101 ORACLE_PATH=0:0:0:0:0:0:0 ORACLE_PROPERTY='oracle-gaps.report' ORACLE_UNIT='random seed: a declaration fault: brokenOwner' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t '^oracle-gaps\.report(?: | > )random seed: a declaration fault: brokenOwner$'

What the evidence shows:

  • For code that runs when the module loads (module data such as D_OBJ), the model judges by the plan's tests only (main's rule). An owner file whose only tests are not the plan's (the console test, the failing owner's passing pair) counts as no load reach.
  • Production does not follow one rule here:
    • In this counterexample, module data owned by files a and b, whose plan tests are all nondeterministic, was judged by some deterministic test that is not the plan's: not-distinguished.
    • In CI seed -555480425 of "a failing owner under its parent's config", module data owned only by file b, whose only tests were the failing owner's suite, was unreached.
    • In the fixed seed at fd32d67f, a model that counted those tests was wrong the other way (indeterminate, owed not-distinguished).
  • The runner runs with isolate: false, so the load's background row may depend on which file of a context loads the module first. The model does not represent that.

Before #176, the failing owner's file was blocked whole, so this was not visible. Block per law now lets that file's passing pair judge.

The question for the maintainer: should the model learn the runner's load-reach rule, or should this case be recorded as a stated limit of the e2e oracle until the CLI records load reach per file?

This issue was written by Isaac.

主要言語
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 を短くまとめたダイジェスト。