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
{{ message }}
Repository navigation
Commit a8351f6
Browse filesBrowse the repository at this point in the historyBrowse files
go vet ./... # static analysis. Always run before tests.
13
-
go test -race -count=1 ./... # tests with race detection
13
+
go test -race -count=1 -timeout=30m ./... # canonical tests with race detection
14
+
go run ./scripts/testsuite -workers 4 # same suite in isolated processes
14
15
```
15
16
17
+
Run vet before either test command. CI uses the same race-enabled suite on all three OSes, with process-isolated shards and a `Tests complete` manifest/result gate. The runner's JSON artifacts include test inventories and timings; scheduling hints never exclude tests. Do not add `t.Parallel` to tests that change Git mocks, cwd, or environment variables.
18
+
16
19
No Makefile, no code generation, no external linter config. Standard Go toolchain only.
go build -o gh-stack .# build (produces ./gh-stack binary)
12
12
go vet ./... # static analysis. Run before tests.
13
-
go test -race -count=1 ./... # all tests with race detection
13
+
go test -race -count=1 -timeout=30m ./... # canonical tests with race detection
14
+
go run ./scripts/testsuite -workers 4 # same suite, isolated parallel processes
14
15
```
15
16
16
-
Always run `go vet` before `go test`. CI runs both on every push/PR across ubuntu, windows, and macOS (`test.yml`).
17
+
Always run `go vet` before `go test` or the parallel test runner. CI runs vet and the complete race-enabled suite on every push/PR across ubuntu, windows, and macOS (`test.yml`). Windows and macOS use process-isolated shards; `Tests complete` checks the combined manifests and results. No tests are excluded to shard the suite.
18
+
19
+
The parallel runner discovers tests from compiled binaries, retains ordinary `go test` support, and writes JSON timing/result artifacts to the printed temporary directory (`-output` selects a parent). Its `-workers` limit bounds test processes; children use `-test.parallel=1`. Scheduling weights in `scripts/testsuite/timings.go` affect balance only, never test membership.
17
20
18
21
There is no Makefile, linter config, or code generation step. The standard Go toolchain is all that's needed.
19
22
@@ -134,7 +137,7 @@ if errors.As(err, &exitErr) { ... }
134
137
135
138
| Workflow | Trigger | What it does |
136
139
|----------|---------|-------------|
137
-
|`test.yml`| push to main, PRs |`go vet` + `go test -race -count=1 ./...`on 3 OS matrix|
140
+
|`test.yml`| push to main, PRs |`go vet` + full race-enabled process shards on 3 OSes; verified completion gate|
138
141
|`release.yml`|`v*` tags | Cross-platform precompiled binaries via `cli/gh-extension-precompile`|
139
142
|`docs.yml`| push to main (docs/**) | Builds Astro/Starlight docs, deploys to GitHub Pages |
0 commit comments