random seed: generated (seed 4): a timeout classification counterexample, on main too
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript
- 领域
- testing
调研方向
Start with the replay command in the issue, using packages/oracles and the supplied seed, path, and Vitest options; compare its result on main with the reported campaign failure. The cause is not established, and the issue names hang cut and idle sampling under load as candidates. Done means identifying and reproducing the timeout classification mismatch and adding evidence that distinguishes the cause.
由索引模型根据 Issue 内容生成。
描述
Summary
The random unit random seed: generated, with ORACLE_SEED=4, finds a timeout-classification counterexample. Main fails it too, so under the M phase-1 rule it is filed, not blocking (P4).
- Campaign (fix/model-work-bound at 39f776c4, on an Arclet, 1 Vitest worker): property failed after 2 tests and shrank twice. Law
classificationatcli:src/sut.ts:f0:33:delete-call#0: timeout, owed indeterminate. - Replay of its printed path (
ORACLE_PATH=1:2:1), twice each on main (eec7f77) and on fix/model-work-bound (6c813287): it fails every time underauthored mutants, withthe authored mutant a1 is unregistered-kill, owed timeout.
The replayed path fails under another law than the campaign's first failure. It is the same on main and on the branch, so the branch's model change (work counted in probe code) does not cause it. Both failures concern a timeout: the model owes a timeout where the CLI reports another outcome, or the reverse.
Replay
cd packages/oracles && ORACLE_SEED=4 ORACLE_PATH=1:2:1 ORACLE_PROPERTY=oracle-gaps.report ORACLE_UNIT='random seed: generated' pnpm exec vitest --run --config oracle-gaps/vitest.config.mjs gap-report-oracle -t "^oracle-gaps\.report(?: | > )random seed: generated$"
(The printed Replay line omits the config, #108.)
Not known
I did not establish the cause. A hang cut or the idle sampler under load are candidates; see the Windows idle gap in the Limits and #99.
- 主要语言
- JavaScript
- 星标
- 5
- 派生
- 1
- 平均合并
- 8 小时 31 分钟
- 30 天内合并 PR
- 60
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TanStack/oracles 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
channels:edit check:passed
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
swc-project/swc-next-issues#490 ·
-
feedback simulation workshop
难度 2/5 1-3 小时 新手友好度 69/100
githubnext/gh-aw-workshop#5826 ·
维护者通常 1 天内回复