mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-08 08:53:43 +08:00
Martin Vogel
1c16786b4b
The Windows pr-smoke uses test-infrastructure/vm/vm-smoke.sh, the Windows analog of smoke-local.sh, which had the same three staging gaps the Unix fix closed: its required-sidecar check, fixture copy, and zip member list all omitted cbm-integrations.json, so the served archive lacked the asset and install/ uninstall failed closed with "integration assets missing". Plus one Windows-specific spot: vm-smoke.sh copies the smoke binary into $SMOKE_DIR and runs smoke-test.sh against it there, but the asset only reached $FIXTURE_DIR — so Phase 14 (which hand-stages the binary and drives an uninstall, resolving the asset next to the binary) missed it. Now staged next to the binary in $SMOKE_DIR as well. build.sh already places it next to build/c/*.exe, so the non-artifact source is $(dirname BINARY_SRC); artifact mode takes the release copy. Member set + order in the zip mirror scripts/package-release.sh (Windows). vm-smoke.sh lives under test-infrastructure/, outside the license gate's scan set, so the cbm-integrations.json/LICENSE adjacency raises no ScanCode finding there. Syntax-checked; vm-worktree-manifest, smoke-fixture and windows-bundle contracts pass. The Unix smoke already runs clean through all 16 phases; this mirrors that staging onto the one path I cannot exercise locally. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
test-infrastructure/ — the local venues
The local half of the 3-OS CI ladder. Every leg here runs the SAME canonical
scripts CI runs (scripts/test.sh, build.sh, smoke-local.sh,
soak-legs.sh, vm-smoke.sh — see scripts/README.md); this directory only
provisions containers and the Windows VM. The venue-parity contract
(tests/test_venue_parity_contract.sh, Step 0j of every test leg) fails the
build if a venue grows its own harness logic — here or in the workflows.
Entry points
| venue | entry | notes |
|---|---|---|
| Linux (arm64 + amd64) + cross-compile | ./run.sh <leg> (--help for the leg list) |
Colima only — Docker Desktop is broken on this machine. A clean-disk preflight (scripts/ci/preflight-docker.sh) runs before every leg: GitHub runners are ephemeral with a known-free 14 GB disk, so the long-lived VM is swept back to that shape first. |
| Real Windows (UTM ARM64 VM) | vm/win.sh <command> (win.sh help) |
Same preflight idea (scripts/ci/clean-test-residue.ps1), plus CI's protected per-user TEMP root. Wine (run.sh windows) is a compile check only — never a substitute for the VM. |
| macOS | run the canonical scripts natively | scripts/test.sh, scripts/build.sh, scripts/smoke-local.sh … |
The ladder (before any push)
scripts/test.sh— macOS native (or--suites …while iterating)./test-infrastructure/run.sh full— Linux arm64 test/build/TSan/smoke/portable + mingw cross-compile (+amd64,soak-linuxas needed)vm/win.sh test-par·guards·smoke-install·soak— the real-Windows legs
Infra unavailable = a run blocker to escalate — never a silent bypass.
Fidelity guarantees (what makes local predictive of CI)
- Same scripts, same sequence, same flags — platform specifics (e.g. the CLANGARM64 trap-UBSan default) live inside the canonical entries, applied identically everywhere.
- Same environment shape — protected TEMP roots, sandboxed smoke, clean builds with the content-verified ccache (a hit is byte-identical to a cold compile; caches only accelerate, never change results).
- Same starting disk — preflights sweep residue and BLOCK below the runner's 14 GB floor (a quietly full disk fails inside install paths and masquerades as a product bug).
- Known, deliberate residuals — runner physics (4 vCPU vs local cores, shared tenancy), Defender ON in the VM vs OFF on GitHub runners, no TSan on Windows anywhere, no ASan runtime on native ARM64 Windows (trap-UBSan + PageHeap stand in).
See vm/README.md for VM provisioning and day-to-day VM mechanics.