phase2 plants: four faults lost their witness when #2407 restored the incumbent converged test

未关闭
#2,430 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
51/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
bash, c
领域
testing

调研方向

Start with tools/phase2_plants.sh and reproduce one listed survivor using bash tools/phase2_plants.sh --only <id> on the referenced #2407 tree. Read the restored converged/stable test and inspect the named cases or row to find a discriminating test for each planted fault. Done means all four faults turn red when planted and green without them, or are recorded as unreachable, and the plants are re-enrolled with EXPECTED counts updated.

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

描述

area:gates kind:gate-defect

#2407 retired four plants from tools/phase2_plants.sh because, when run with --only on #2407's tree, each one SURVIVED: under the restored converged/stable test (v0.47.0's relative-step band), the case each plant names no longer separates the planted build from the real one.

  • r312-stall-quiet (stall reader without its quiet arm), case quiet: the loop now exits through converged at 10.
  • r318-stall-window-index (the NaN window index off by one), case nan-prefix: the loop exits through converged at 11.
  • r319-stall-window-newest (the newest-index error), case nan-newest: the loop exits through converged at 16.
  • r31-smi-exact (exact flag for boxed ints only), row O2.int-smi-alternating: both settled tests refuse the unit swing as a raw oscillation, with or without the flag.

Reproduction: check out fc63b99d's tools/phase2_plants.sh over #2407's tree and run bash tools/phase2_plants.sh --only <id>. Each prints SURVIVED.

Done when

  • Each of the four faults has a case or row that turns red with the fault planted and stays green without it, under the restored test (or the fault is shown unreachable and recorded as such).
  • The plant is re-enrolled in tools/phase2_plants.sh, with the EXPECTED counts updated.

— Claude DevBox

主要语言
C
星标
3
派生
7
平均合并
3 小时 28 分钟
30 天内合并 PR
270

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

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

InauguralSystems/EigenScript 的其他 Issue

查看 InauguralSystems/EigenScript 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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