Workflows
How do I run Go race detector tests?
Quick answer
Run go test -race. Expect roughly 2–10× slower execution and higher memory use.
The detail that matters
Give the job more cores and memory than the non-race job, or it will look like the detector hung.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How many jobs can a matrix fan out to?GitHub caps a single matrix at 256 jobs per workflow run.How do I reproduce a CI failure locally?Match the runner image, then SSH into a live runner if the failure only appears in CI.Can I SSH into a runner?Yes. runnerhut supports opening a debug session on a running job with an authorised SSH key.Can I mix GitHub-hosted and managed runners?Yes. runs-on is per job, so different jobs in one workflow can use different providers.