-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/tools/go/packages: data race in (*loader).refine #31749
Comments
Edit: my race seems to be different from this race. Will pull into its own issue (#32154). Simple reproducer:
Where
As far as I've been able to determine, the presence of dot imports as well as the presence of a test package are relevant. This looks like a proper bug in go/packages, not "just" an issue with its tests. /cc @ianthehat and @matloob again, for good measure. |
Here's another one: |
I'm not sure why this has the |
This looks like the same race that was reported in #30107. |
This is causing a lot of test failures in the TryBots for @ianthehat, @matloob: can someone prioritize a fix for this? |
Looking at this now |
It's not obvious to me what the issue is so I'm going to disable the tests on (tip, race) while I debug. |
Change https://golang.org/cl/200819 mentions this issue: |
A change in go/types has uncovered a race in go/packages. While we debug, ignore those tests when running on tip with -race to make the builders green. This change will be reverted as soon as the issue is fixed. Updates golang/go#31749 Change-Id: I96f0b30a1bc203a5c36a2ce30c943583b7f8035a Reviewed-on: https://go-review.googlesource.com/c/tools/+/200819 Run-TryBot: Rebecca Stambler <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Jay Conrod <[email protected]>
The original race reported is #34919. I am not sure about the storage.googleapis.com links that Bryan posted - some of those look different. |
In the newer races Bryan posted, the three race detector failures are all #34921. The non-race panic about the algorithm going wrong could easily have been caused by those races too. I think combined #34919 and #34921 explain all the failures in go/packages linked in this thread. /cc @griesemer |
Change https://golang.org/cl/201838 mentions this issue: |
Was closed by mistake, https://golang.org/cl/201838 mentioned #34921 by mistake. Though now that #34921 and #34919 are fixed, this bug may have been fixed as well. @matloob Could you look into this and see if you can still reproduce this issue (and if not, close it)? Thanks. |
Still racy; filed #35049. |
Seems to be fixed now. (At least, CL 202538 passed in the TryBots.) |
https://storage.googleapis.com/go-build-log/2b8cbc38/linux-amd64-race_ad38befa.log
The text was updated successfully, but these errors were encountered: