docs(CI): 修 run 46 暴露的 doc-links 违规,并更正「CI 工作区跨 run 复用」错话
run 46(你推的 dc5d6a0):L0.5 = Success,40 runner、3188/3188 断言、fail=0; L0 = 47 Passed / 1 Failed / 2 Skipped —— A 方案确实生效:`ui-golden` 在 CI 里第一次 真编模拟器、真比像素,菜单 8 状态 + 内容页 40 页全过转绿(SYSTEM 命中机器级 `DTU_SDL2_DIR`)。你补跑的 -SetEnv 顺带把 `DTU_MS_COVERAGE` 也钉上了,两个变量成对。 剩下那 1 根红是我自己造的:新加的症状行里写了 gitignored 的构建产物路径,本机 存在、干净检出不存在,于是 `doc-links`「本地过、CI 挂」——正是本文 §4.1.2 记的那 一坑,我一边写它一边踩了它。修法按工具给的提示走(不把不入库的运行时路径当 引用写)。验证没有用本地:在一份**从未构建过模拟器**的干净克隆里先复现(1 处 问题、同一行),再验证修完(0 问题、RC=0),那才是 CI 的处境。 撤回两句错话:我先前写「毒缓存会跨 run 存活」「`-ffd` 是因为 runner 工作区跨运行 复用被忽略文件」——对 CI 都不成立。实测 run 44 / 45 / 46 的 L0 工作区目录哈希互不 相同,**每个 job 一个全新目录**,各付 137~161 s 全量拉取(612 s 的 run 里约 5.4 分钟 是两次拉取)。自愈检查仍然必要,但真正的暴露面是**同一个 job 内**(`ui-golden` 与 板端导航自检共用同一份构建目录,前者中断会毒到后者)以及本机日常开发。§4.5、 §5.3 的 `-ffd` 依据、§7 行与 `ci.yml` 注释四处同步改成实测口径;变更记录按规矩不动 历史行,只在上方加更正行。 自查:两个 job 的检出正文仍逐字一致(7147 字符)、run 块非 ASCII 计数 0、`uses:` 0; 本地暂存钩子 HOOKS_RC=0;干净克隆里 `doc-links` 0 问题、`check_ids` 不可判定 1166 = 上限(未增)。预期这一笔推上去 L0 归零失败——那是自 run 23(10-12)以来第一次 两个 job 全绿。
This commit is contained in:
+10
-4
@@ -236,8 +236,11 @@ jobs:
|
||||
if ($c.Code -ne 0) { $c.Lines | ForEach-Object { Write-Host " $_" }; Write-Host '::error::detached checkout failed'; exit 1 }
|
||||
$rr = Invoke-DtuGit -G @('reset', '--hard', '-q', $env:DTU_REPO_SHA)
|
||||
if ($rr.Code -ne 0) { Write-Host '::error::reset --hard failed'; exit 1 }
|
||||
# -ffd, deliberately not -ffdx: -x would delete IGNORED files, and the runner
|
||||
# reuses those across runs (pip / pre-commit caches live in the workspace).
|
||||
# -ffd, deliberately not -ffdx: -x would delete IGNORED files. Within ONE job several
|
||||
# hooks share this directory (pip / the simulator build tree), and local reruns reuse
|
||||
# it. NOTE measured 2026-10-27: CI gives every job a FRESH workspace (the L0 dirs of
|
||||
# run 44/45/46 all differ, each paying a full 137-161 s fetch), so -ffd is a safe
|
||||
# default, not a speed trick.
|
||||
$cl = Invoke-DtuGit -G @('clean', '-ffd', '-q')
|
||||
if ($cl.Code -ne 0) { $cl.Lines | ForEach-Object { Write-Host " $_" }; Write-Host '::error::git clean failed'; exit 1 }
|
||||
$head = (Invoke-DtuGit -G @('rev-parse', '--short', 'HEAD')).Lines -join ''
|
||||
@@ -624,8 +627,11 @@ jobs:
|
||||
if ($c.Code -ne 0) { $c.Lines | ForEach-Object { Write-Host " $_" }; Write-Host '::error::detached checkout failed'; exit 1 }
|
||||
$rr = Invoke-DtuGit -G @('reset', '--hard', '-q', $env:DTU_REPO_SHA)
|
||||
if ($rr.Code -ne 0) { Write-Host '::error::reset --hard failed'; exit 1 }
|
||||
# -ffd, deliberately not -ffdx: -x would delete IGNORED files, and the runner
|
||||
# reuses those across runs (pip / pre-commit caches live in the workspace).
|
||||
# -ffd, deliberately not -ffdx: -x would delete IGNORED files. Within ONE job several
|
||||
# hooks share this directory (pip / the simulator build tree), and local reruns reuse
|
||||
# it. NOTE measured 2026-10-27: CI gives every job a FRESH workspace (the L0 dirs of
|
||||
# run 44/45/46 all differ, each paying a full 137-161 s fetch), so -ffd is a safe
|
||||
# default, not a speed trick.
|
||||
$cl = Invoke-DtuGit -G @('clean', '-ffd', '-q')
|
||||
if ($cl.Code -ne 0) { $cl.Lines | ForEach-Object { Write-Host " $_" }; Write-Host '::error::git clean failed'; exit 1 }
|
||||
$head = (Invoke-DtuGit -G @('rev-parse', '--short', 'HEAD')).Lines -join ''
|
||||
|
||||
Reference in New Issue
Block a user