Windows e2e: stdout has one more gap line than the expected count (fixed seed 4/10, noTypescript)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript
领域
testing

调研方向

Start from the failing Windows job log for fixed seed 20261105: a declaration fault: noTypescript and compare the 169 oracle-gaps: stdout lines against the expected 168 gaps to isolate the extra line. Then trace where that checkpoint emits gap lines in the e2e harness, using the earlier #73 Windows stdout-count fix as the closest precedent. Done means the fixed-seed Windows run reports exactly 168 lines and the source of the extra line is explained.

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

描述

windows

Job: https://github.com/TanStack/oracles/actions/runs/43661845394/job/132652674703 (Windows gap report end-to-end oracle, fixed seed 4/10, on #73 at 104376d)

Test: fixed seed 20261105: a declaration fault: noTypescript (9.0 min on windows-latest)

Error:

oracle-gaps.report violated at checkpoint "stdout" (law: greppable stream).
Difference: the stdout has 169 gap lines for 168 gaps: ["oracle-gaps: gap not-distinguished L4 sut.ts:M1 ` process.env.NODE_ENV !== 'production' ` → ` undefined `", "oracle-gaps: gap not-observed L4 sut.ts:M2 ` !== ` → ` === `", "oracle-gaps: gap unreached L6 sut.ts:M3 ` false ` → ` undefined `", ...]

What this is: the stdout of the run has one more gap line than the expected count of gaps, on win32. It is the same family as the earlier Windows stdout-count breach (fixed on #73 for authored mutants). The extra line has not been identified; the full list of 169 lines is in the failing run's log.

Not: the oracle's expected count for this history. Linux runs pass.

Found while reviewing #73 (its body links this issue). Non-blocking: Windows end-to-end is non-blocking under C entry (c) until #79.

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