Repository navigation
[PR] fix(ci): a verified pretest-cache HIT must also touch dist mtimes to now (#4548) - #4549
Closed
ranxianglei wants to merge 1 commit into
Closed
ranxianglei wants to merge 1 commit into
ranxianglei wants to merge 1 commit into
Conversation
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5488-pr.4549.501eacfThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4549.tgz
npm install -g packageInstall instructions are refreshed on each push. |
This was referenced Oct 24, 2026
Owner
Author
|
(ai: zhipuai-lb/glm-5.3) 陈旧票清理(第三批动作①):目标 issue #4548 已关。为避免重复劳动关闭本 PR;如判断有误请直接 reopen 并留言。 |
This was referenced Oct 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(ai: zai/glm-5.3)
Fixes #4548
这是啥问题?
master 自 10:31Z 起所有测试道红(#3330 的 #3325 mtime 守卫撞上 #4377 的 pretest 缓存):actions/cache 恢复的 kernel/dist 带归档旧时间戳,marker 内容哈希判新鲜跳过重建,守卫按 mtime 判 stale → golden drive 拒跑。全链路见 issue。
修复(2 文件 +63/-2)
scripts/ci-pretest-cache.mjs:HIT 分支在 marker 验证通过后递归utimes整个 dist 树到当前时间——「被验证新鲜的 dist 也必须是 mtime 新鲜的」,对 test: rebaseline storage-render goldens after remove-absorb (#3309) #3325 守卫/tsup 增量等一切 mtime 消费者成立。守卫本身不动(对本地忘重建的防护仍正确)。tests/ci-pretest-cache.test.ts:新回归测试完整复现事故时序(构建→dist mtime 拨回过去→源文件更新)→ 断言 HIT 不重建 + dist mtime 越过源 mtime;带前置条件断言(恢复后必须先看起来 stale,负向控制)。验证
node --import tsx --test tests/ci-pretest-cache.test.ts8/8 绿(含 7 个既有 CI Windows test lane takes 20+ minutes: every leg does a full rebuild of kernel/pi-subagents dist — the sharding is way | CI windows 测试车道 20+ 分钟:每条腿都全量重建 kernel/pi-subagents dist,分片也太粗 #4360 契约测试);runPretestCache(HIT 路径)无异常。能否合并?
纯 fix、单模块(scripts/ci-pretest-cache.mjs + 其测试)、带回归钉、不动配置面/不动 kernel/。按 §7.4 属可自动合并档,但仍等 owner。合并后 master 下一个全量跑即恢复绿(无需清缓存——HIT 路径现在会 touch)。