random seed: an ambiguous authored mutant: field-drop judged not-distinguished, owed indeterminate (seed 333199054), on main too

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
backend, testing

调研方向

In packages/oracles, replay the reported seed and path with the provided Vitest command, then inspect the trace for src/sut.ts:D_OBJ:30:field-drop#0 and compare the expected and reported outcomes. The issue says the cause is not established, so start by determining why the model expects indeterminate while the CLI reports not-distinguished. Done when the counterexample is understood and the replay no longer shows that classification difference.

由索引模型根据 Issue 内容生成。

描述

Summary

The random unit random seed: an ambiguous authored mutant found a classification counterexample on seed 333199054 (path 0:0:0:0:0:0:0) in the random shard 1/3 of PR #90's seed measurement (run 43778881284). The CLI reports src/sut.ts:D_OBJ:30:field-drop#0 as not-distinguished, and the model owes indeterminate.

It reproduces with the same seed and path on origin/main (4d3c8a9): the replay job replay 333199054 an ambiguous authored mutant in run 43782377713 fails with the same difference. So it is a base defect, not caused by PR #90. Filed under P4.

Replay

cd packages/oracles && ORACLE_SEED=333199054 ORACLE_PATH=0:0:0:0:0:0:0 ORACLE_PROPERTY=oracle-gaps.report ORACLE_UNIT='random seed: an ambiguous authored mutant' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "^oracle-gaps\.report(?: | > )random seed: an ambiguous authored mutant$"

The printed Replay line omits the config (#108).

Checked against #115 and #99

#115 (stream law) and #99 (wall-clock cut) do not name field-drop or indeterminate, and #99 has no mention of the indeterminate outcome. The cause is not established. It may be a timing cut that gives indeterminate on one side only, but that is a guess until the trace is read.

主要语言
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 摘要。