You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Flaky test: WAL custom-cap checkpoint case asserts byte-exact file size, intermittently red on 5 CI shards #4489
AssertionError: WAL must be truncated to the configured cap at the autocheckpoint (left 1095952 bytes, cap 1048576) —— 残留超配置上限 47376 字节(~11.6 页),断言容差仅 CAP_SLACK = 4 KiB(一页)。
Refined evidence (from the PR #4485 review follow-up):
Independence from any PR diff is now proven, not just evidenced. The host CI shards ONLY top-level tests/*.test.ts (readdirSync(testsDir), non-recursive, scripts/run-ci-tests.mjs:105); PR [PR] kernel: preserve existing block coverage when merging blocks (#4484) #4485's new test lives under kernel/tests/ (kernel suite lane), so the sharded file list is byte-identical between master and that head → identical LPT partition → the 5 failing shards contain exactly the same files in both trees. Same error bytes across trees ⇒ purely runner-dependent.
Attempt 2 of run 40069753327 failed again (same 5 shards, same test, same left 1095952 bytes), engine logged as node:sqlite/builtin. Two consecutive red attempts on one head vs one red + two green on master: unlucky-draw hypothesis still fits, but this shape clearly needs the house treatment.
Activity
ranxianglei commentedon Oct 24, 2026
(ai: vllm-qwen/qwen3.8-27b)
Refined evidence (from the PR #4485 review follow-up):
tests/*.test.ts(readdirSync(testsDir), non-recursive,scripts/run-ci-tests.mjs:105); PR [PR] kernel: preserve existing block coverage when merging blocks (#4484) #4485's new test lives underkernel/tests/(kernel suite lane), so the sharded file list is byte-identical between master and that head → identical LPT partition → the 5 failing shards contain exactly the same files in both trees. Same error bytes across trees ⇒ purely runner-dependent.left 1095952 bytes), engine logged asnode:sqlite/builtin. Two consecutive red attempts on one head vs one red + two green on master: unlucky-draw hypothesis still fits, but this shape clearly needs the house treatment.scripts/run-ci-tests.mjs+scripts/ci-failure-shapes.mjsclassify recoverable strict-timing shapes under runner load and retry the shard once (CI flake:test (windows-latest, 24) 单文件文件级失败:子测试零执行、异常被吞为 'test failed' #3029 drain family, CI: windows-latest node-22 shard 2 intermittently red on timing-sensitive e2e tests under load (rotating flakes: issue760, #4079, storage-full-flip #3818) #4161 timing-budget family, windows-22-1 lane randomly red: during test cleanup, unlink index.db hit an EBUSY external lock, couldn't survive tmp-rm | windows-22-1 车道随机红:测试清理期 unlink index.db 遇 EBUSY 外部锁,熬不过 tmp-rm 的 9.6 秒重试梯子(#2799/#2908 族复发) #4347 transient-lock family — each with the "deterministic break reproduces on retry" guard). This WAL custom-cap signature is NOT in the classifier, so it goes straight red. Suggested fix therefore has two parts, mirroring CI: windows-latest node-22 shard 2 intermittently red on timing-sensitive e2e tests under load (rotating flakes: issue760, #4079, storage-full-flip #3818) #4161's belt-and-suspenders: (a) make the assertion convergence-driven (bounded extra ingests untilwalSize <= cap + CAP_SLACK) so the exact-timing assumption goes away at the source; (b) optionally add the signature toci-failure-shapes.mjsas defense-in-depth until (a) ships.ranxianglei commentedon Oct 24, 2026
(ai: vllm-qwen/qwen3.8-27b)
查重: 不重复——按 WAL / journal_size_limit / checkpoint / flaky 失败签名检索 open+closed issue 与近期 PR,无匹配(OP 已声明「查重: 无」,我独立复核确认)。
标签:
bug+scope/ci+p3(CI 抖动噪音类缺陷,无用户可见影响;无客户端涉及)。修复已完成 → PR #4502(Closes #4489)。本地先复现后验证:修前本地跑出与 CI 字节一致的报错(
left 1095952 bytes),修后连续 10/10 通过,typecheck 干净。八问:
CONV_UNITS = 24(一个完整 cadence 周期 20 + 落地滞后 1 + 余量 3,推导写在常量注释里)。关键实测约束:单写者下两类 completed checkpoint 都会把文件精确落回 cap;autocheckpoint 触发点在越过 1000 页的那个 commit 的下一个;更大的单元(1 MiB)不可用——它自己的 extent(~1.15 MiB)截断后仍超 cap+slack,所以循环必须用 128 KiB 单元。未加ci-failure-shapes.mjs分类器签名(上条评论的可选 part b):本 PR 已消除源头,再加就是死代码,且该分类器是字面窄匹配纪律;若合入后签名再现,再作为纵深防御补上。tests/issue3250-wal-checkpoint.test.ts,+37/−10),src/ 零改动。RED/GREEN 判别力保持:对照实验(limit 设为 100 MiB ⇒ truncate 变 no-op,等价 pre-fix 世界)显示文件全程钉在高水位不收缩 → pre-fix 树在新断言下照样红。CONV_UNITS是测试文件内局部常量)。判定:可合并——待 PR #4502 远程 CI 全绿即收工,无阻塞项。
ranxianglei commentedon Oct 24, 2026
(ai: vllm-qwen/qwen3.8-27b)
来源: #4497 分析 CI 红时发现。review PR #4497(durable-mnemon 分类器,与存储域零交集)时对两轮 CI 红做了逐分片日志取证,发现同一失败域还有两条本 issue 范围外的 flaky 签名。按「同失败域 = 同 issue」并入此处管理,不另立项。
新增 flaky 签名(检查清单补充)
media CAS: stale-row sweep releases media refs and mappings (full re-ingest drops the image)(tests/media-cas.test.ts)#1365 apply() attach mode: runtime death with routed evidence — waits the target back, never migrates交叉证据(与本 OP 互证)
left 1095952 bytes)与我独立从同一 master run 40068050438 提取的完全一致(该 run 还挂了 ubuntu 22-1 / 24-1 两个分片的同名用例)。对收敛判定的影响
PR #4502 覆盖 WAL custom-cap 一条。按本轮观察频率,media CAS stale-row sweep 出现次数与 WAL 相当(两 run 合计 6 vs 5),#1365 attach-mode 较低(1 次)。#4502 合入后这两条大概率仍会红分片——建议后续在本 issue 内按同一「收敛驱动断言」思路跟进这两项(或各自独立修复,机制不同不强行合并修法)。
test: #4489 drive the WAL custom-cap assertion by convergence, not a …
test: #4489 drive the WAL custom-cap assertion by convergence, not a …