You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows Go tests became the CI critical path after redundant Linux work was removed. Recent successful jobs spend nearly all of their wall time inside the Go test command, with real SQLite fixture setup and the CGo-heavy DuckDB package competing for four runner cores; adding broad `t.Parallel` calls would increase contention without addressing that work.
The suite now constructs high-cardinality SQLite fixtures transactionally while preserving the production triggers, scale comparisons, and 1,024-row claim boundary they protect. The ordinary database suite deterministically verifies the closed-writer fallback, while the concurrent close/reopen stress case remains in the existing Linux race job. On Windows, DuckDB runs on an independent runner and the main package set avoids verbose log I/O, allowing both long test groups to advance concurrently.
This trades additional Windows runner-minutes for a shorter required-check critical path. The principal review points are the package split in `.github/workflows/ci.yml`, the deterministic/race coverage split in `internal/db`, and the transaction-backed fixtures in `internal/artifact`, `internal/parser`, and `internal/sync`.
Co-authored-by: Wes McKinney <wesm@users.noreply.github.com>
0 commit comments