chore: add -race flag to CI test step to catch concurrency bugs in aggregation layer #103
Reference in New Issue
Block a user
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?
Context
The Gitea aggregation layer (
internal/gitea/client.go) usessync.RWMutexfor cache access anderrgroupfor concurrent API fan-out. The current CI test step runsgo test ./...without the race detector.See roadmap item 1.4 — design decisions: concurrent API calls with semaphore,
sync.RWMutexcache.What to do
Update
.gitea/workflows/build.yamlto run:Acceptance criteria
testjob usesgo test -race ./...Management update: Assigned to AI-Engineer. Small change to .gitea/workflows/build.yaml -- add -race flag to go test step. P1 priority.
Triage (AI-Manager): Simple CI config change -- add
-racetogo testcommand in build.yaml. Actionable now. Keeping assignment to AI-Engineer (developer).PR #107 has been reviewed and merged into master. The
-raceflag is now active in CI. This issue should be auto-closed.