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
cmd/go: go get -u=patch hangs while using CPU while 1.17.1 doesn't #48511
Comments
(sigh) Ok, breaking out |
|
|
I'm planning to look at this again once CL 357169 lands, since it may interact nontrivially. |
While this is a release blocker, I think it's worth pointing out it's not extremely urgent: one can sidestep the issue by using |
I've made some progress tracking this down, but no fix yet. It appears that |
The beta is getting close and this is currently marked as blocking the beta. Any news here? |
Found it. Missed Next step: regression test! |
Change https://golang.org/cl/368136 mentions this issue: |
This seems to be a regression in master since 1.17 was released.
Repro steps below; luckily, I encountered the hang in an open source module repo.
I haven't narrowed down the reproducer or bisected just yet. I think this might be enough information for @bcmills or @jayconrod to have a good guess as to what recent change added this hang.
I tried using
^\
to get a stack trace of the process, but I get seemingly harmless stack traces that show cmd/go doing work, so perhaps the endless loop is at a higher level - for example, loading the same package over and over again.Marking as release-blocker for now, as it looks like a regression.
The text was updated successfully, but these errors were encountered: