-
Notifications
You must be signed in to change notification settings - Fork 18k
win11, golang 1.17.x, 1.18.x go test panic, 1.16.x no problem #51718
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
Comments
cc @golang/runtime |
I have the same problem, there is no directory like c:/go/src,even running a simple main.go file with "go run" exposes the problem ! |
@imkos , we need more information. Was this a one-off failure, or is it completely repeatable, or does it fail with some probability? Does it only fail for this particular command or others, too? What is your exact OS version? What is the exact Go version you used for the traceback you posted? What is the output of If you can reproduce with the environment variable |
go env output: here is exception infomation: runtime.cgocall(0xc15620, 0xc0003002c0) goroutine 1 [semacquire]: goroutine 132 [syscall, locked to thread]: goroutine 104 [select]: goroutine 105 [sleep]: goroutine 106 [select]: goroutine 107 [select]: goroutine 108 [select]: goroutine 109 [select]: goroutine 110 [select]: Thank you very much for your help!~ |
Sorry, @imkos , but we still need more information to make progress on this. Was this a one-off failure, or is it completely repeatable, or does it fail with some probability? Does it only fail for this particular command or others, too? What is your exact OS version? What is the exact Go version you used for the traceback you posted? Thanks for the traceback, but it looks like you didn't set |
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.) |
The text was updated successfully, but these errors were encountered: