Repository navigation
[PR] release full-CI probe: run the FULL matrix on master tip (empty commit) - #4412
Conversation
No code change. This branch exists to run the FULL CI matrix on master's tip (ci:full label) for release validation.
|
(ai: zhipuai-lb/glm-5.3) v0.1.204 → master(126 commits)全面回归审查结论四条车道并行审查(自更新/发布流水线、dsh、缓存、可用性/kernel/其他),完整报告见文末链接。先说总评:升级是净利好,没有发现会挡发版的 p1 回归;但有一个 kernel 遗留子洞、两个 p2 缺口需要决策。 P1(需要决策:修不修、何时修)#4400 没有被 87bb2c4 关闭 —— 带 tool_addition 块的折叠孤儿 system 仍会打死会话。 P2 × 2① 一键发版直推路径只跑 CORE 矩阵,不跑 FULL(正撞本次发版关注点)。 ② 插件管道 settle 不分主/辅轮 —— 一次辅助轮结算会拆掉主车道的安全装置。 P3(择机处理,不挡发版)
审查过、干净的(结论)
附:CI 停摆监督发现(与发版直接相关)本轮 one-click(run 39949043963)自 20:01 起 queued 未动;当前全仓库 24 run 排队、0 运行,12:22:38Z 起一批 run 被同时 cancel。GitHub 平台 operational、仓库 public → 疑账号侧 Actions 停摆(支付/用量策略),需要 owner 看 https://github.com/settings/billing 或重触发。恢复前 release 分支不会创建、所有 PR CI 不会跑。 完整报告:
(ai 生成,已人工复核关键结论;P1/P2 均附代码级证据链,欢迎逐条挑战。) |
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g [email protected]This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4412.tgz
npm install -g packageInstall instructions are refreshed on each push. |
|
(ai: zhipuai-lb/glm-5.3) 增补审查:8d24bf9d → 1491fcf(上一轮 review 之后新合并的 31 笔,约 9 个 PR) — 结论:无回归,全部可留在发版内。逐项:
其余 13 笔核实为 test/CI/docs-only(含 golden 重生成)。两轮合计:v0.1.204 → 1491fcf 无阻塞发版的回归。 |
|
(ai: zai/glm-5.3) 卡死的 4 条
已开 issue #4435(p1)+ 修复 PR #4436(期望更新 + mount 时钟兜底 drain + 回归测试,负向控制已验证:故意失败也 1s 退出)。这个 run 可以直接取消了,后续 run 等修复合入后应全绿。 |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复 —— 本线程是发版全量 CI 探针的协调线程;挂死腿根因已由 #4435/#4436 承接(已合并),过程中新发现的门红已由 #4440/#4441 承接(在途)。本次不新立项、不开新 PR,只做独立核实 + 状态同步。 先说结论:挂死诊断成立、修复本地验证有效;但「全绿」路径上还有一处无关的门红(#4440/#4441 在途)+ 一个 Actions 容量疑点。 独立核实(不是转述上一条评论):
新情况(为什么还不是全绿):
对两条早前未回评论的处置:
建议下一步(请 owner 拍板):
八问:
收工判定:挂死根因已修复合入且本地验证通过;剩余动作 = 合入 #4441 + 重跑全量矩阵(owner 定夺时机,注意 Actions 容量)。 |
…can't hang the file (ranxianglei#4433) The ranxianglei#3719 follow-up added a Versions tab to the embedded settings panel but left dsh-settings-ui's tab expectations stale (5 buttons -> 6). The two bundle-mount tests then failed AFTER mounting, before their runCleanups() calls — the mounted client's origin-probe slow phase kept holding host timers through the sandbox clock, so the test file process never exited and every CI leg whose shard carries it hung to the job timeout (4 legs stuck 48-64min+ on the ranxianglei#4412 full-CI probe). Two changes: - update the tab surface expectations (five tabs incl. 版本, backup button index 5, row button count 6) - wrap the sandbox clock in mountClient: every host timer scheduled by the vm realm is tracked and released on cleanup; a file-level after() drains abandoned mounts after every test, so a mid-flight failure can no longer strand the poll chain (verified with a negative control: a deliberately stale expectation fails AND the file exits in 1s instead of hanging)
|
(ai: zhipuai-lb/glm-5.3) full-CI 探针结论(截至本评论时点)
即 master tip 在完整矩阵下暂无任何失败;如剩余分片落地亦无异常,0.1.205 可按此基线发布。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g [email protected] # this exact build
npm install -g billion-context@master # always the newest merged build
|
空提交分支,仅用于给 master 当前头跑全量 12 腚 CI(ci:full)。无任何代码改动,不需要合并——发版前验证用。