CI: we should have a test phase that runs `go test -race`
Open
area/pipeline
engineering item
test automation
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
This came up in PR#9368 - we had a data race bug in `Lazy`.
We should setup a CI task for this - we used it all the time in the Go AMQP SDK and in the Go Azure SDK. If we haven't tested this way before it's possible there'll be some work to fix any tests or code, so this task might be larger than just "add a YAML block", but it'll be worth it.
Contributor guide
Research direction
Start by tracing the repository's CI configuration and existing test jobs, then review PR#9368 for the Lazy data-race context. Add a CI phase that runs `go test -race`, run it across the repository, and address any test or code failures it exposes so the new job passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100