-
Notifications
You must be signed in to change notification settings - Fork 18k
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/cmd/goimports: hangs in uninterruptible sleep #19225
Comments
tcoffee-google, is there anything special or interesting about |
Are you using one of Google's internal FUSE filesystems? If so I'd mail the Google internal mailing lists for tips. |
I have the same issue on Windows, it's a larger project. Command I recently did Also, Any ideas? |
After a reboot the issue persists. What's interesting though is that |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
I'm facing this too. |
@arnavsharma93, this is a closed bug and we don't track closed bugs. If you want to open a new bug, please include a lot more info. Piling on this overloaded bug just gets distracting. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.7.3 linux/amd64
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/usr/local/google/home/tcoffee/go"
GORACE=""
GOROOT="/usr/lib/google-golang"
GOTOOLDIR="/usr/lib/google-golang/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build134362667=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
What did you do?
Run
goimports -w myfile.go
.What did you expect to see?
Program termination.
What did you see instead?
The goimports process goes into uninterruptible sleep, blocking on disk I/O (status 'D') for at least 20 minutes, and hence cannot be killed without rebooting.
The text was updated successfully, but these errors were encountered: