determinism: the CLI's heartbeat list depends on wall-clock timing, so five determinism units fail on main

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

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

@KyleAMathews がすでに取り組んでいます。

2026年11月15日 から。

  • #90 @KyleAMathews による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
22/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript, typescript
領域
testing

調査の方向性

Start by reproducing one failing unit with the command given: cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: a declaration fault: brokenOwner", and read the History: {...} payload plus the structural diff against $.heartbeats. Then read the determinism units themselves and the CLI heartbeat recording code they exercise, alongside the related issue #84, to see where wall-clock ordering enters. Done means the five listed units pass reliably, but the fix path (excluding the heartbeat set from comparison versus a test-only pause point) is undecided and needs a maintainer call first.

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

説明

Summary

Five determinism units of the end-to-end gap oracle fail on main (35422e3). Each one runs a history twice and compares the two traces. The traces differ in the CLI's heartbeats list, which records which busy mutants beat. Whether a mutant beats depends on wall-clock timing, so the comparison is timing-dependent. Found by the determinism units that CI-1 moves onto pull requests (PR #90).

Failing units (main 35422e3, one Arclet, one Vitest worker)

  • determinism: constructed history: an edit sequence over the witness module
  • determinism: constructed history: every outcome class
  • determinism: constructed history: a declaration fault: brokenOwner
  • determinism: constructed history: a declaration fault: noTypescript
  • determinism: generated 2

Evidence

Each failure is at observation 0 (cli). A structural diff of the two full traces (captured with a scratch patch that prints the untruncated texts, since the message keeps 2,000 characters) differs only in $.heartbeats. For brokenOwner, one run's list includes sut.ts:M177 and the other's does not. The other units show the same kind of shift in the list.

Replay

Determinism units have no replay line. Run one unit with the project's command:

cd packages/oracles && pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "determinism: constructed history: a declaration fault: brokenOwner"

The history is printed in the failure message (History: {...}).

Why it matters

The register's "determinism under load" decision (2026-11-13) says that an oracle driver must not rely on wall-clock ordering. This comparison records a timing-dependent set, so it fails under load even when the CLI is deterministic. #84 is the reach side of the same timing (the heartbeat state's count per shard). This issue is the determinism side.

Open question for the maintainer

Either the determinism comparison should leave the heartbeat set out, since "each beat is observed as its mutant and file, not how long or how often it beat" (the law's own wording), or the beat set should be made deterministic through a test-only pause point as in #84's proposed fix. Not decided here.

主要言語
JavaScript
スター
5
フォーク
1
平均マージ
8時間 31分
マージ済み PR(30日)
60

環境構築

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

はじめの一歩

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

TanStack/oracles のほかの issue

TanStack/oracles の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

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

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