-
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: go get -d fails with "no go-import meta tag" #27730
Comments
Are you running multiple Does this occur only for |
Note that |
It's only happened for golang.org/x paths so far. Only running one I think it may just be flakiness on the servers. |
Sure, I'm updating go on the build servers now. I'll report back if I notice the issue again. |
I just saw this issue on my CI, on Go 1.11, using docker image golang:1.11-alpine. A rerun seems to "fix" it.
The full log from the job below:
|
I believe that a fix to #28194 will also address this symptom. Closing as duplicate. |
Seeing the same issue via bitbucket pipelines on all "golang.org/x/.." dependencies |
Please subscribe to #30619. |
Hello, I've noticed that occasionally our CI builds have been failing during
go get
. It doesn't seem to be one package that's causing this to happen, and the issue usually resolves itself quickly, but the flakiness is causing alerts in our environments. I was asked to create a new issue in https://github.com/golang/go/issues/27622#issuecomment-420312891Two examples follow:
What version of Go are you using (
go version
)?go version go1.9 linux/amd64
Does this issue reproduce with the latest release?
It's hard to say because it's flaky. I'm currently updating our CI servers to 1.10.
What operating system and processor architecture are you using (
go env
)?What did you do?
Ran
go get -d ./... 2>&1
as part of a jenkins job.What did you expect to see?
Nothing. Successful update
What did you see instead?
Errors above (both are golang.org/x/ packages)
The text was updated successfully, but these errors were encountered: