chore(go): enable race detector in tests #4622
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
casibbald
approved these changes
Jan 26, 2025
This was referenced Jan 26, 2025
This was referenced Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes
What changed?
CGO_ENABLED=1)Why was this change made?
I am trying to figure out why the Go tests sometimes blocks "forever" in CI. Example: https://github.com/weaveworks/weave-gitops/actions/runs/12973902776/job/36183126193. And I have a feeling this problem is related to Goroutines, missing error handling and/or races. I want to eliminate the latter, so I suggest we enable the race detector for the tests.
How was this change implemented?
How did you validate the change?
Release notes
Documentation Changes