Repository navigation
[PR] ci: register tests/storage-durability.test.ts in LIVE_FILES (#4333) - #4334
ranxianglei wants to merge 2 commits into
Conversation
#4177 landed the storage durability trio but its new suite spawns child processes without registering in scripts/live-files.mjs, so the #1248 SPAWN_RE tripwire fails every CI run — master aa198fe is red and every branch rebased onto it inherits the failure. Concurrency review: the suite only spawns `node -e setTimeout` probes (no port binding) and isolates data in mkdtempSync dirs; slot 31 / zone band 19811 is free. Fixes #4333.
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.5142-pr.4334.2f0f160This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr4334.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Since #4177 the storage contract suites transitively import acp-kernel at runtime (backend -> store -> runtime-status -> knobs -> config), and tsx resolves it to kernel/dist — which this job never built. Mirror the prerequisite the main test matrix (run-ci-tests pretest parity) and ci-e2e-dsh.yml already carry. Fixes #4336.
|
(ai: zhipuai-lb/glm-5.3) 追加第二处 master 红:mysql-contract 车道(#4336)——#4177 给 修法=照抄 ci-e2e-dsh.yml:90 的已验证模式,job 里补一行 本 PR 现在两件事:①LIVE_FILES 登记(Fixes #4333)②mysql-contract kernel 构建(Fixes #4336)。两个都是从 #4177 继承的 master CI 红,合并即恢复 master 全绿。 |
|
(ai: zhipuai-lb/glm-5.3)
本 PR 可关闭(superseded by #4350)。另:#4334 头 job 上 windows-22-1 的两条 EBUSY 失败与本 PR 改动无关——master 9e2d217(不含本 PR 任何改动)同签名失败,根因与修复见 #4347。 |
(ai: vllm-qwen/qwen3.8-27b) 判定:不在本分支修 —— 本 PR 已被完全取代(两个 commit 均冗余),红车道属于在途跟踪的存量缺陷。按自动修复车道规则(每 PR 最多 2 次;失败需要设计决策或不是小修时发判定并停),本轮到判定为止。 1. 是什么问题 2. 什么原因导致的
机制有两个竞争假设,都已立项跟踪:
3. 影响范围与严重程度 4. 怎么处理的(为什么不直接修)
5. 是否有回归问题 6. 是否破坏缓存 7. 是否改了设计方向 8. 是否引入新配置 判定:#4334 关闭(superseded by master 133cdd2 + PR #4350);windows-22-shard-1 红车道等 #4350 的 CI 结果 + owner 对 #4338/#4347 机制之争的裁决。 |
) Since ranxianglei#4177 the storage suites transitively import acp-kernel at runtime (store.ts -> runtime-status -> knobs -> config); tsx resolves it to the built dist, so the mysql-contract job dies with ERR_MODULE_NOT_FOUND on a fresh runner. Same prerequisite the main test matrix already has via run-ci-tests' pretest step. Cherry-picked from ranxianglei#4334.
…glei#4347) Fixes ranxianglei#4347. The windows-22-1 lane hit the ranxianglei#2799/ranxianglei#2908 EBUSY family twice in 24h (PR ranxianglei#4334 head job + master 9e2d217, byte-identical signatures): Windows AV/indexer briefly locks a freshly-written index.db past tests/tmp-rm.ts' ~9.6s retry ladder, failing the two corrupt-index.db tests with 'EBUSY: resource busy or locked, unlink ...'. The classifier judged that concrete -> red, no retry, blocking unrelated PRs. Adds a third recoverable shape 'cleanup-lock' beside ranxianglei#3029 (swallowed deaths) and ranxianglei#3665 (event-loop drain): when EVERY failing subtest carries a transient-lock errno on an unlink/rmdir through a rimraf teardown stack, retry the whole shard once and exit 0 only if the retry is green. A deterministic lock (a genuine handle leak) reproduces on the retry and still fails, so no regression can be masked; a raw user-code unlinkSync EBUSY (no rimraf frames) stays concrete and unretried. Both real failed logs classify cleanup-lock; the real ranxianglei#4336 regression log stays concrete. Unit coverage asserts both directions (ranxianglei#3617).
(ai: zhipuai-lb/glm-5.3)
#4177 落了 storage durability trio,但新测试
tests/storage-durability.test.ts用了child_process.spawn却没登记scripts/live-files.mjs的 LIVE_FILES——#1248 绊线让 master 自身 CI(aa198fe61)与所有基于新 master 的分支全部红。本 PR 一行修复:按字母序登记该测试(slot 31 / 端口带 19811)。
并发假设已核对(登记前置要求):
node -e "setTimeout() => {}, 60000)"探针子进程(锁文件第二进程检测),不绑任何端口;mkdtempSync隔离,删除BILI_STORAGE_UNIFIED后走自身环境;Fixes #4333