random seed: an edit sequence through the daemon: authored mutant a2 runs to its backstop (timeout, owed killed), seed 964713679 on #99

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

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

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

評価

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

調査の方向性

Start with the e2e oracle command and seed in the counterexample, then inspect the authored mutants law at the cli checkpoint and the history details in the issue. The report identifies a timeout in file b's authored:a2 copy, but the cause is still unknown and history replay depends on #157. Done means reproducing and explaining the timeout; the issue assigns this investigation to #99's author for a later follow-up round.

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

説明

Counterexample

A random seed of the e2e oracle on #99 at 83a0b3a8 (pool, then twice more, and on macOS: reproducible):

ORACLE_SEED=964713679 ORACLE_PATH=0 ORACLE_PROPERTY='oracle-gaps.report' ORACLE_UNIT='random seed: an edit sequence through the daemon' GAP_E2E_SHRINKS=0 vitest run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t '^oracle-gaps\.report(?: | > )random seed: an edit sequence through the daemon$'
  • Law authored mutants, at checkpoint cli (the cold run): the authored mutant a2 is timeout, owed killed. Its result is {"outcome":"timeout","cause":"backstop"}.
  • File b's copy for authored:a2 runs to its backstop: 20.05 s, where the limit is 20 s plus 3 s × 0.018 s. Its file's unmutated run takes 0.018 s.
  • The history (cut at 2,000 characters in the log) has:
    • two functions, if x > 4 push and push, owned by a and b;
    • a test of file a with input 5, and a test of file b with input 1 on f1;
    • authored: {stmt: 0, kind: apply}, secondAuthored: true, ordinary: true, contexts: 4, budget: one;
    • cliPath: spaced, unbuiltDep: true, packageType: commonjs, configFile: vite.config.cts, concurrentStart: true.
  • The same seed passes on main 97a4e7a, but there it draws a different history, because #99 shifts the draws. So base attribution needs a replay by history (#157), which is not built yet.

What is known

  • The copy is not idle by state. If it were, it would be killed by no progress. It also has no call budget (an authored copy counts no calls).
  • The copy either loops synchronously, or waits before any test starts. Before a test starts the sampler does not judge idle; an example is a module fetch over the runner's RPC (#148).
  • It is not caused by #99's clocked-by-state hook: with that hook's completion record disabled, the unit fails the same way.

Owner

#99's author, in the next round on the deterministic-cuts follow-ups. Replay the full history on main once #157 lands; if main fails it too, this does not block #99 (M, "Main's determinism failures").

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