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
runtime/race: RaceAsFunc3 and many others are flaky #14086
Comments
Also Windows: windows-amd64-race at 970ce1c |
Related: #14079 /cc @aclements for statistics. All these race flakes seem very recent. |
|
There are many race-related flakes on the dashboard. I feel like shipping a Go 1.6 at this point would mean shipping a potentially broken race detector. @dvyukov, any clue why? |
I ran stress -p1 ./race.test on linux/amd64 from tip and got 8 / 32 failures. Then I reverted the most obvious candidate I could think of -- c5f0f88 ("runtime/race: update race runtime") -- and I've had 0 / 16 failures. And as I was about to submit this comment, it ticked over to 1 / 22 :-) but it still seems like the update didn't help. |
CL https://golang.org/cl/18968 mentions this issue. |
Ran some longer tests, seems less clear. I guess it should be possible to bisect over the last few months of development given that it was a cm/dist problem preventing the tests from being run rather than anything preventing go test -race runtime/race from working. Would take a while though. |
FreeBSD race flake:
http://build.golang.org/log/e9536db3f2c81412f3cc2225ba19c60d34ad06e2
The text was updated successfully, but these errors were encountered: