-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: reference to nonexistent package when importing package starting with "go." #49606
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
seems to be an issue when the package name doesn't match the directory name, and the module has a |
Should we switch back to trying to reserve "shape" as a standard lib package name (your proposal #49268) - no dots in "shape", so can't possibly be a user-package path, right (unlike go.shape)? |
Hmm, I'm not sure this particularly has to do with using |
Looking at the |
We are facing the below failure while trying to build https://github.com/etcd-io/etcd repo with latest upstream golang:
Sample failed Run: https://prow.ppc64le-cloud.org/view/s3/prow-logs/logs/postsubmit-master-golang-etcd-build-test-ppc64le/1461496375937077248 |
Change https://golang.org/cl/365834 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
No, this has not been released yet.
What did you do?
I’m importing
go.opentelemetry.io/otel/semconv/v1.7.0
package and the CI pipeline for tests with gotip broke somewhere between the November 3rd and 5th.Note that I can’t reproduce the issue with
go.uber.org/zap
package, which also starts withgo.
prefix.What did you expect to see?
Build succeeds and the program prints
exception
string.What did you see instead?
I’ve bisected the issue to commit 7f2463c (cc @randall77).
Log
The text was updated successfully, but these errors were encountered: