Repository navigation
[PR] fix(e2e): pin dual-write storage in the native-pi sandbox (#6480 follow-up) - #6567
ranxianglei wants to merge 5 commits into
Conversation
#6480 flipped the storage default to pure-SQLite (JSON envelope writer off unless dual-write is explicitly requested). This suite's persistence assertions all walk the sandbox's session JSON files (sessionFiles()), so the pure-sqlite default left them structurally failing on master — the 'real pi package-native lane' CI leg has been red since the flip. Pin dual-write in the sandbox config, the same pattern the suite already uses for BILI_PI_INLINE=0: the assertions verify what they have always verified (envelope presence, folded blocks, pluginAgent binding); the pure-sqlite default is covered by the storage-json-writer-off* unit suites. ensureConfigTemplate() never overwrites an existing file, so the pre-seed survives plugin bootstrap.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.10141-pr.6567.145073dThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr6567.tgz
npm install -g packageInstall instructions are refreshed on each push. |
The real-dsh headless profile lane went red on master the same way the pi package-native lane did: #6480 made pure-SQLite the default (jsonWriter off), so the JSON session envelopes this lane's waitForPersistedSession()/persistedSessions() traversal asserts on are no longer written. The lane's own rigs pre-write their sandbox billion-context.json without a storage key, so they silently inherited the new default. Same test-only pin as the pi lane (e2e-native-pi): an explicit storage.{unified: full, jsonWriter: on} for a lane whose assertions deliberately read the JSON envelope layout. Verified locally with the real dsh 0.2.0-rc.2: both files 2/2 after the pin, red before.
…e default (#6480) The suite-wide baseline (tests/preload-storage-baseline.mjs) pins BILI_STORAGE_UNIFIED ??= "legacy" for the legacy-written corpus, but this suite asserts the fresh-install default posture — the exact #6480 pure-sqlite flip the storage-sqlite-default notice advertises. Under the CI preload chain the pin hid the notice and two subtests failed deterministically (red in every shard leg containing the file). Drop the inherited pin so the production default applies, per the preload's own pin-yourself contract.
…igs too (#6480) Same regression as the native-pi/dsh lanes: #6480's pure-sqlite default made the jsonWriter off by default, so the lanes' persisted-session file walks (sessionFiles()/persistedSessions()) saw zero JSON envelopes and their persistence assertions failed. Pre-seed the sandbox config with storage:{unified:"full",jsonWriter:"on"} like the other lanes. Verified locally (pi 0.83.6): without the pin the opencode lane fails 2 of 4 and the codex-ws lane fails 1 of 6; with it, both are fully green.
# Conflicts: # tests/notice-registry.test.ts
(ai: vllm-qwen/qwen3.8-27b) Merge-conflict resolved — PR is now mergeable (no conflicts)Merged The one conflict — Verification honesty: the mirror check-cache was stale this run (still reporting the pre-push sha 结构化八问
收工判定:冲突已解、PR 已可合并( |
[ework] CI fix verified green ✓ |
#6480 (pure-SQLite default, 2026-11-13) turned the JSON writer off by default. Four e2e lanes plus one unit suite assert on persisted JSON envelopes via plain filesystem walks (sessionFiles()/persistedSessions()) and went red deterministically on master; this test-only PR pins the sandbox configs back to dual-write (storage:{unified:"full",jsonWriter:"on"}) so those assertions keep testing what they were written to test.
What turns green on master (cron FULL matrix)
Method
Scope
Test-only (+18 +21 +26 +6 lines across 6 test files). No src/ changes. Cherry-picked as e891908 into PR #6546 and #6551 so their shard legs containing the notice-registry file go green on the next run.