Skip to content

fix: register issue2752 forward-partial-outcome suite in LIVE_FILES (#2896) - #2898

Merged
ranxianglei merged 1 commit into
ranxianglei:masterfrom
YunzhouLi-hub:2026-10-12_live-files-issue2752
Oct 12, 2026
Merged

ranxianglei merged 1 commit into
ranxianglei:masterfrom
YunzhouLi-hub:2026-10-12_live-files-issue2752

Conversation

@YunzhouLi-hub

@YunzhouLi-hub YunzhouLi-hub commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Closes #2896

问题

#2782 合入 master 时带入了 process-spawning 套件 tests/issue2752-forward-partial-outcome.test.ts,但未在 scripts/run-ci-tests.mjs 的 LIVE_FILES 注册(#2816 静态门)。master push 的 CI 中 test job 为 skipped,所以 master 表面全绿;而所有 PR 的 merge ref 上 npm test 必红(实测 #2878/#2881/#2883/#2890 四条 matrix 腿同错)。

修复

在 LIVE_FILES 数组按字典序插入一行:

     "tests/issue1958-routed-warn.test.ts",
+    "tests/issue2752-forward-partial-outcome.test.ts",
     "tests/issue760-percall-conversation.test.ts",

并发假设审查(按错误信息要求)

行为变更

无生产行为变更;仅 CI 调度清单登记。旧行为:该套件从未在 CI process-spawning 相位执行(门直接 die);新行为:正常进入并行相位执行。

Closes #2899(同一机制的第二份报告,源自 #2893 分析;一行修复同时覆盖)

@YunzhouLi-hub

Copy link
Copy Markdown
Contributor Author

CI 全绿(CLEAN)。这个一行修复解锁当前所有开着的 PR(#2878/#2881/#2883/#2890 的 test matrix 都被 #2782+静态门的叠加回归卡红),合入后各 PR 合并一次 master 重触发即可恢复。随时可合。

@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.318-master.c1b83c3 (rolling master tag).

npm install -g billion-context@0.0.318-master.c1b83c3  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

YunzhouLi-hub added a commit to YunzhouLi-hub/billion-context that referenced this pull request Oct 12, 2026
YunzhouLi-hub added a commit to YunzhouLi-hub/billion-context that referenced this pull request Oct 12, 2026
YunzhouLi-hub added a commit to YunzhouLi-hub/billion-context that referenced this pull request Oct 12, 2026
@ranxianglei ranxianglei mentioned this pull request Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants