-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make use of the race detector #1430
Comments
An env variable which is enabled on the ci makes sense |
How about GOFLAGS ? |
@strk I submitted a PR for it. |
Yes, I meant something like that.
I'm not sure $(GOFLAGS) would expand to the env variable, give it a try.
If it doesn't work, try ${GOFLAGS}
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
The race detector is helpful for discovering race conditions in concurrent programs. The easiest way I can think of is to add a new target or some kind of env. variable in the Makefile to enabe
-race
. We could also begin running try.gitea.io with the race detector enabled.Edit:this is not just a proposal, but also a call for ideas about how we are going to do it.
The text was updated successfully, but these errors were encountered: