Repository navigation
[PR] fix CI hygiene: root lockfile kernel 0.0.159→0.0.160 + 4 unused exports in corrupt-index-child - #4416
Merged
Conversation
…ly symbols lock-sync: kernel/package.json is 0.0.160 but the root package-lock.json kernel entry still said 0.0.159 — the bump missed the lockfile regen, so 'npm install --package-lock-only' dirtied the tree and lock-sync failed. unused-exports: tests/corrupt-index-child.ts exported ENGPROOF_CHECK_NAMES / BANNER_CHECK_NAMES / CorruptIndexCheck / CorruptIndexVerdict but only the child module itself uses them (the parent tests import the derived ENGPROOF_CHECKS/BANNER_CHECKS arrays and the view helpers). Drop the export keyword; parents stay green (web-storage-banner, storage-engine-proofs both fail=0 locally).
ranxianglei
changed the title
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5287-pr.4416.fabc58dThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4416.tgz
npm install -g packageInstall instructions are refreshed on each push. |
The lock-sync guard regenerates BOTH lockfiles (root + kernel); the bump missed kernel/package-lock.json's two version lines too.
…_FILES The #4216/#4249 storage work made tests/storage-engine-proofs.test.ts and tests/web-storage-banner.test.ts spawn the corrupt-index-child helper, but they were never added to LIVE_FILES — the run-ci-tests SPAWN_RE tripwire (#3182/#1248) failed every ubuntu leg in 20s. Append-only per the slot note: existing zone bands are untouched.
This was referenced Oct 23, 2026
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.771-master.1491fcf # this exact build
npm install -g billion-context@master # always the newest merged build
|
This was referenced Oct 23, 2026
ranxianglei
pushed a commit
that referenced
this pull request
Oct 23, 2026
Line-count LPT balanced bytes, not seconds: process-spawning suites cost orders of magnitude more per line than pure assertion files, and the 'perfectly balanced' layouts still produced 5min..37min legs from equal byte counts (windows 22-2/22-3 vs 22-1/22-4 on the same run). With #4384's linger cut landed the per-file wall times are stable enough to weight the partition by MEASURED duration: - scripts/ci-shard-partition.mjs: fileWeight = last measured ms per file (scripts/ci-shard-weights.json), new files fall back to lineCount x msPerLineFallback (median ms/line); same deterministic total LPT otherwise. - scripts/ci-shard-weights.json: 840-file table measured post-#4384 (single-file node --test runs, VM, ~66min serial total); local-env hangs capped at the 150s timeout and listed under timedOut, local rc=1 env-fails excluded. Regenerate via scripts/measure-test-durations.mjs when shard balance degrades. - run-ci-tests.mjs delegates partitionAll to the module (this script has top-level side effects and cannot be imported by tests). - ci.yml: windows-22 CORE 3->5 shards, windows FULL 3->5 (both node versions) — measured max shard drops 1984s->794s serial (concurrency c=4 per shard => ~7min worst-leg target incl. setup). Four NEW check names appear (windows 22/24 shards 4/5); branch protection must add them before they gate merges. Cherry-picked from closed PR #4361 (commit 0569781, stranded when the PR was superseded by #4377; picked up per owner invitation in the #4361 thread). The sibling LIVE_FILES commit (d06d192) is already on master via #4416 and is not included. Closes #4437
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.
Two master guard failures blocking the release full-CI probe (#4412):
lock-sync:
kernel/package.json= 0.0.160 but rootpackage-lock.jsonkernel entry = 0.0.159 — bump missed the lockfile regen. Fixed bynpm install --package-lock-only(single version-line change).unused-exports:
tests/corrupt-index-child.tsexported 4 symbols nobody imports (ENGPROOF_CHECK_NAMES,BANNER_CHECK_NAMES,CorruptIndexCheck,CorruptIndexVerdict); parents import only the derived arrays. Dropped theexportkeyword.Local verification:
node scripts/check-unused-exports.mjs→ clean; both importer suites (web-storage-banner, storage-engine-proofs) fail=0.kernel-change: sync kernel/package-lock.json version lines to 0.0.160 (lockfile metadata only, no kernel source change)