Skip to content

1.8.0: Go support in opt-in dynamic checks

Choose a tag to compare

@catfish-1234 catfish-1234 released this 10 Nov 02:54
· 16 commits to main since this release
b39c7a1

Go modules with *_test.go files now run in the opt-in dynamic checks through go test -count=1 -json ./... under the existing bubblewrap write/network isolation, with GOPROXY=off and GOTOOLCHAIN=local so runs never fetch modules or toolchains.

Which checks execute for Go: DY001 (baseline test regression) and DY005 (inconsistent repeated test, now recognizing an added time.Sleep). Which do not: DY002 probes and DY004 mutation-lite remain Node/Python-only; DY003's expectation-literal recognition is JS/Python-shaped and does not fire for Go. A changed go.mod/go.sum stops a dynamic run as inconclusive, matching the existing dependency-manifest pinning.

Verification, with exact execution scope: full vitest suite green locally (batched runs; lint clean; verify:pack passes from a fresh tarball install) and PR/main CI green on macOS/Ubuntu/Windows plus the proctor self-check and tuned-dev gates. On CI runners (no bubblewrap), the 4 unit-level Go tests (JSON event parsing, adapter selection, test-location) pass on every platform/Node leg while the 5 sandbox integration cases skip — end-to-end Go execution was verified only on Linux with Go 1.26.6 and bubblewrap 0.6.1, not cross-platform. Those authored integration cases run through the real sandbox: a removed guard pinned by a baseline test flags DY001 naming example.com/age::TestRejectsOutOfRange; an honest red-to-green fix stays silent; a build failure reports skipped with a reason and no finding; a deterministic authored regression fixture (a time.Sleep-added test with visit-counter outcomes, not a real scheduling flake) flags DY005; the working tree is left untouched.

Evidence integrity: named results come only from go test -json pass/fail events carrying a Test field; package-level pass/fail lines, skips, cached results (-count=1 disables caching), empty packages, and build/package-level failures produce no named evidence — build failures and exit-without-named-failure states report skipped/inconclusive, never a clean pass or a synthetic finding. Duplicate or conflicting named outcomes make the run inconclusive.

Contract-verified through the sandboxed worker only: no live-harness, catch-rate, or all-language claims. Modules whose dependencies are not already in the local module cache fail honestly rather than fetch, and cold Go build caches can approach the default 60s dynamic budget on large modules (reports skipped, never a finding). The historical Windows 15/16 count-loss incident remains an unresolved caveat; see docs/UNRESOLVED-INTEGRITY.md.