ci: add -race flag to go test in .forgejo/workflows/test.yml (regression gate for #14 + future concurrency bugs) #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Cellblock CI currently runs
go test ./...without the-raceflag (see.forgejo/workflows/test.yml). The data race fixed by #14 (single-closer send lifecycle) was caught only because Surveyor explicitly mutation-tested the invariant locally with-race. A reintroduction ofclose(p.send)would pass CI green, defeating the substrate-hardening intent of the fix.Surveyor flagged this during PR #19 review as a non-blocking should-consider for the cellblock-hardening ledger.
What
Add
-raceto thego testinvocation in.forgejo/workflows/test.yml. The race detector is the only practical gate against concurrent-send/close-on-channel regressions.Acceptance criteria
.forgejo/workflows/test.ymlgo teststep includes-raceclose(p.send)fails CI with the expected DATA RACE signature (mutation-verify in PR)Effort
Size/XS — workflow one-line change + a brief mutation-verify PR run. Single-chamber pickup.
Duplicate of #21 (Engineer filed in parallel from PR #19 review). Closing in favor of #21 as the canonical tracker — same intent, same Surveyor review-catch as the source. The decision-tree on #21 already covers the framing; this issues body adds nothing distinct.