Skip to content

[PR] test: pin storage mode in compress-from-store (CI red — same class as #4076) - #4113

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-21_compress-from-store-mode-pin
Oct 21, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-21_compress-from-store-mode-pin

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

(ai: zhipuai-lb/glm-5.3)

什么坏了

master(11ef088 起,PR #4104 ci:full 率先完整跑到)三个 shard-1 runner(ubuntu22/1、ubuntu24/1、win22/1)在 tests/compress-from-store.test.ts 上确定性红:

根因

与 #4076/#4077 同一类:该文件没钉存储模式。CI runner 预载 preload-storage-baseline.mjs(BILI_STORAGE_UNIFIED ??= legacy)后,两个 unified-store 恢复测试(full-mode 故事)走 legacy 读路径 → 恢复不出来 → refused/SQL 错。本地 standalone(默认 full)永远绿,所以 #3983 合并时没看见。本地双条件复现:不带 preload 4/4 绿;带 preload 2 fail——与本 PR 修复后双条件 4/4 绿对照。

修法

文件顶部钉 process.env.BILI_STORAGE_UNIFIED = "full"(storage family 纪律);no-store 拒答测试自建 enabled:false store,模式无关,不受影响。

影响面

仅测试文件,零产品代码。修复后 CI 的 3 个红 shard 全绿(其余 shard 本来就绿)。

备注

这是该纪律的第三个漏网实例(#4076 两族 → #4087 win EBUSY → 本条)。#4077 里已建议过:值得做一个静态门禁(storage-family 文件清单或 new SessionStore({enabled:true 出现即要求钉模式),防止第四次。

…e full-mode stories

CI preload (legacy) flips the story under them: the two unified-store
recovery tests fail under BILI_STORAGE_UNIFIED=legacy (refused instead of
applied / ERR_SQLITE_ERROR), deterministic on every shard-1 runner
(ubuntu22/1, ubuntu24/1, win22/1 of PR #4104). Same class as #4076/#4077:
storage-family tests pin their mode instead of inheriting the runner default.
@ranxianglei ranxianglei changed the title test: pin storage mode in compress-from-store (CI red — same class as #4076) [PR] test: pin storage mode in compress-from-store (CI red — same class as #4076) Oct 21, 2026
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-21_compress-from-store-mode-pin (9d9f6dc)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.4903-pr.4113.cd22199

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr4113.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit da1c0c8 into master Oct 21, 2026
31 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.713-master.da1c0c8 (rolling master tag).

npm install -g billion-context@0.0.713-master.da1c0c8  # 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant