Add -count=1 to the canonical Go make test example #45

clawbot · 2026-08-10T15:51:50+02:00

clawbot commented

2026-08-10 15:51:50 +02:00

Answers #44: the canonical Go make test target omitted -count=1, so Go replayed cached successful results and the target could exit 0 having executed no test. Every repository that copied it inherited that false green.

The change adds -count=1 to both go test invocations in the example in REPO_POLICIES.md, with a short paragraph saying why, and records the step in TODO.md. It defeats only the test-result cache, not the build cache, so it costs the suite's runtime and no recompilation. It is independent of the Docker layer cache that #26 addresses.

Rebased onto current main; the check is green. Repositories pick it up the next time each vendors the canonical files.

Model: opus-5 (change); fable-5-1 (this description)

Answers https://git.eeqj.de/sneak/prompts/issues/44: the canonical Go `make test` target omitted `-count=1`, so Go replayed cached successful results and the target could exit 0 having executed no test. Every repository that copied it inherited that false green. The change adds `-count=1` to both `go test` invocations in the example in `REPO_POLICIES.md`, with a short paragraph saying why, and records the step in `TODO.md`. It defeats only the test-result cache, not the build cache, so it costs the suite's runtime and no recompilation. It is independent of the Docker layer cache that https://git.eeqj.de/sneak/prompts/issues/26 addresses. Rebased onto current `main`; the check is green. Repositories pick it up the next time each vendors the canonical files. Model: opus-5 (change); fable-5-1 (this description)

clawbot added 1 commit 2026-08-10 15:51:50 +02:00

Add -count=1 to the canonical Go make test example (closes #44 )

check / check (push) Successful in 13s

Details

3933e6bdfa

The canonical Go `test` target in `REPO_POLICIES.md` omitted `-count=1`, so
Go replayed cached successful results and the target could exit 0 having
executed no test. Every repo that copied it inherited the false green.

Both invocations get the flag; the rerun needs it so a failure is
reproduced rather than replayed.

clawbot added the needs-review label 2026-08-10 15:51:52 +02:00

sneak was assigned by clawbot

2026-08-10 15:51:55 +02:00

clawbot referenced this pull request

2026-08-10 15:52:27 +02:00

Canonical Go make test example omits -count=1, shipping a false green to every repo #44

sneak commented

2026-08-30 06:22:45 +02:00

@clawbot unmergeable

~~clawbot referenced this pull request 2026-09-03 20:28:09 +02:00~~

Go test cache is a second, independent source of unearned greens: canonical `make test` lacks `-count=1` #32

~~clawbot referenced this pull request 2026-09-03 20:29:13 +02:00~~

Canonical Go make test example omits -count=1, shipping a false green to every repo #44

clawbot added needs-rework and removed needs-review labels 2026-09-03 20:29:45 +02:00

sneak was unassigned by clawbot

2026-09-03 20:29:47 +02:00

clawbot self-assigned this 2026-09-03 20:29:47 +02:00

clawbot force-pushed go-test-count1 from 3933e6bdfa to c937cd7a4c

2026-09-03 22:13:10 +02:00

Compare

clawbot added needs-review and removed needs-rework labels 2026-09-03 22:59:52 +02:00

clawbot added needs-rework and removed needs-review labels 2026-09-03 23:04:31 +02:00

clawbot referenced this pull request

2026-09-03 23:05:03 +02:00

PROPAGATION: roll the -count=1 Go test-cache fix (#44) into every consuming Go repo — as ONE commit per repo #57

clawbot added 1 commit 2026-09-03 23:06:44 +02:00

Document the Go test-result cache as a second, independent cache

check / check (push) Successful in 5s

Details

d7fb86f0a0

Go's test-result cache sits below the Docker layer cache that issue #26
addresses. CHECK_EPOCH forces the RUN make test step to re-execute, but
GOCACHE baked into earlier image layers survives into the re-executed
step, so go test can still do no work. Record that these are two
separate defects so a fix for one is not recorded as covering the other.

Also correct the TODO.md Completed Steps date to the landing date, which
matches the REPO_POLICIES.md last_modified front matter.

Closes #44