-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: test gets hung #27720
Comments
SIGQUIT will dump the goroutine stack traces. Does the go command not exit after SIGQUIT ? Or it was already hung and you entered SIGQUIT to break out ? |
The latter - I SIGQUIT after 20 minutes. |
Interestingly this is no longer happening locally on my laptop, but IS still occurring reliably on our CI. |
Very interesting that |
From the dump, it looks like all the runners are waiting on the mutex to be freed. |
Unfortunately not, this is in a private corporate repository. Sorry I can't provide much more information than the above. One other piece of data that may be useful: prior to this, |
Just a shot in the dark. Have you tried |
I have yes, but also the CI doesn't keep state around, so it downloads from scratch each time. |
@alecthomas thank you for reporting this issue and @agnivade too! I'll also tag @randall77 @aclements @ianlancetaylor since this involves the runtime scheduling and signals. |
Okay, I think I've find out what the problem is. It's partially my fault, but the behaviour is still very surprising. This is replicable by having the Go source extracted at the root of my package prior to running |
I'm not sure that there's anything more to be done here. Please let us know if you have ideas. |
What version of Go are you using (
go version
)?go version go1.11 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
Completion, error, or a timeout message.
It's probable this was a network issue of some sort, but
go mod download
completed successfully.What did you see instead?
One CPU is pegged at 100% usage, and the go command doesn't complete.
The text was updated successfully, but these errors were encountered: