Skip to content
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: panic when argument doesn't match any packages [1.10 backport] #28724

gopherbot opened this issue Nov 11, 2018 · 1 comment


None yet
3 participants
Copy link

commented Nov 11, 2018

@odeke-em requested issue #28696 to be considered for backport to the next 1.10 minor release.

Thanks for reporting this @nicksnyder and for working on it @mark-rushakoff!

This is a new panic in Go1.11.*. On Go1.10, it printed out

$ go run nonexistent/...
go run: no go files listed

and now on Go.1.11, it panics as reported

$ go run nonexistent/...
go: warning: "nonexistent/..." matched no packages
panic: runtime error: index out of range

goroutine 1 [running]:
cmd/go/internal/run.runRun(0x195d2e0, 0xc0000ae0b0, 0x1, 0x1)
	/Users/emmanuelodeke/go/src/ +0xc01
	/Users/emmanuelodeke/go/src/ +0x7d4

@gopherbot please open a backport tracking issue for 1.11.


This comment has been minimized.

Copy link

commented Nov 11, 2018

For some reason Gopherbot opened up a backport issue for Go1.10.6 yet this problem only exists on Go1.11. I'll close this, please feel free to reopen if need be.

@odeke-em odeke-em closed this Nov 11, 2018

@dmitshur dmitshur modified the milestones: Go1.10.6, Go1.10.7 Dec 13, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.