Repository navigation
fix: windows 全量矩阵收尾挂起——三个受害 harness 补 closeAllConnections + 60s 超时,EBUSY 不再掩蔽真错 - #3526
Merged
Merged
Conversation
… the three victim harnesses The cancelledByParent cascade class (pi-omp-fork-adopt 9x, plugin-fork 34x, plugin-bypass 3x today): teardown awaits once(server,"close") while an undici keep-alive socket (idle, unref'd) keeps the server closing forever — the event loop drains and the runner force-cancels the whole file. Applies the owner-sanctioned aa56257 pattern (closeAllConnections + 60s timeouts) to the three files that actually hung, keeps withMode's rmrf EBUSY from masking the real test error, and logs swallowed sidecar sqlite close failures.
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.4171-pr.3526.02f1f27This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr3526.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Owner
Author
|
(ai: zhipuai-lb/glm-5.3) 验收通过 ✅ ——
说明:期间两次 run 被 cancel 不是失败——master 在 08:42/08:49 合入 #3519/#3524 触发 synchronize,新 run 取代旧 run(正常并发取代);最终判定以合并头上的 39018820451 为准。 本地佐证:pi-omp-fork-adopt + plugin-bypass + persist-guard-ownership 32/32,plugin-fork 48/48(151s),typecheck 干净。 可以合并(合并不归我,按仓库规矩人工合)。 |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.531-master.3f513c2 # this exact build
npm install -g billion-context@master # always the newest merged build
|
This was referenced Oct 17, 2026
Merged
Closed
Closed
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: zhipuai-lb/glm-5.3)
Fixes #3525
改了什么
照搬 owner 今天在 aa56257 治 lane-decisions-matrix 的同一套既定模式,应用到今天全量矩阵里实际挂掉的三个文件:
closeAllConnections?.()(强杀全部连接,收尾的once(server,"close")不再等一个空闲+unref 的 keep-alive socket 到天荒地老);挂 harness 的用例加 60s 超时,残余挂起以带栈超时浮出而非无声连坐。为什么只有全量矩阵红
挂起=收尾等 close 事件,而 keep-alive socket 空闲后被 undici unref,事件循环排空,runner 判定「promise 未决但循环已排空」→ 同文件整批 cancelledByParent(pi-omp-fork-adopt 9 连坐、plugin-fork 34 连坐、plugin-bypass 3 连坐,签名一致,重跑复现)。CORE 与全量的分片组合不同,普通 PR 的 CORE 矩阵跑不中这套文件组合,所以只有 ci:full / 定时跑暴露。完整机制与证据链见 #3525。
验证
风险面