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

未关闭
#91 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@KyleAMathews 已经在做这个了。

开始于 2026年11月15日。

  • #90 来自 @KyleAMathews —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
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 分钟
30 天内合并 PR
60

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TanStack/oracles 的其他 Issue

查看 TanStack/oracles 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。