Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

strict_differential: the pixel differential is silently off because its renderer probe expects 1 and gfx_open returns true

未关闭 适合新手
#1,825 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
c, shell

调研方向

从tools/strict_differential.sh第1593行附近的renderer探测比较开始,然后仅将tests/test_asan_gfx.sh作为相关背景进行查看,因为那部分属于#1723。更新脚本,使只有false会禁用像素一致性,true会运行差分测试,而任何其他输出都会导致失败。验证像素行会在正常工作的renderer上运行,并且人为植入的gfx_read故障会使脚本以非零状态退出。

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

描述

area:gates area:gfx found-by:critic kind:gate-defect

Found while verifying the #1758 R1.2 builder's fix on PR #1776 (phase2-numbers, commit 95ce2fed). On main, nothing has changed.

Since gfx_open returns a bool (#1637), print of (gfx_open of [8, 8, "pixdiff-probe"]) prints true. tools/strict_differential.sh:1593 still compares the probe's last line with "1". So on a machine with a working renderer it sets NO_RENDERER=1, prints NOTE: no renderer — pixel identity is OFF, and finishes OK without running the pixel differential.

Checked on main 0740af03: the probe prints true on Xvfb :99 and with SDL_VIDEODRIVER=dummy. The line is unchanged on origin/main 540f0bcf.

The builder's one-time plant on the branch: a pixel fault in gfx_read passed the old checker (exit 0, pixel rows skipped) and failed the fixed one (37/37 pixel rows differing).

tests/test_asan_gfx.sh's grep "sdl-present: 1" has the same cause; that half is #1723.

Done when

  • On main, tools/strict_differential.sh runs its pixel differential whenever the probe prints true, and fails, rather than reporting "no renderer", on any probe output other than true or false.
  • Planted fault, in the PR: a pixel fault in gfx_read makes tools/strict_differential.sh exit nonzero on a machine with a renderer; restored, it exits 0 with the pixel rows counted.
主要语言
C
星标
3
派生
7
平均合并
11 小时 16 分钟
30 天内合并 PR
267

环境准备

在 Codespaces 中打开

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

从这里开始

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

InauguralSystems/EigenScript 的其他 Issue

查看 InauguralSystems/EigenScript 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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