-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/vet: inconsistent import #15728
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
Can you give us instructions for how to reproduce the problem? CC @griesemer for a go/importer crash. |
Unfortunately no. Program that I am go vet-ing is too big and I don't even know where to start reducing it. There are no clues in this backtrace. Any pointers? |
Furthermore, I can't reproduce it any more. I have turned off go vet execution to be able to work on a program and now, when I have turned it back on, it does not panic. Possibly it is somehow connected to update of a go lang. I had some other go-tip version installed before today. Today i went to ~/go, did
and saw that go vet crashes. Then I commented go vet execution in Makefile and continued my day. Anyway, I am saying that possibly after upgrading go lang and without recompiling everything (I didn't delete $GOPATH/pkg, go vet crashes. But after recompiling everything, go vet is fine. |
Thanks for the update. Closing until the problem can be reproduced. |
This is probably a duplicate of #15491 which was fixed a while back. |
I just started facing this issue, after upgrading to Go 1.7beta1:
Should I open a new issue? |
@griesemer nevermind, after cleaning my GOPATH the issue is gone. Thank you! |
I also saw this after an upgrade to Go 1.7. It would be nice if the output mentioned the possibility of incompatible files in |
@aaronlehmann Did you have libraries installed that you compiled with some non-release version; i.e., a version built off tip, rather than an official release? If so, those libraries may have been compiled with a buggy compiler. We don't really make guarantees for compilers that are not from official releases. If not, I'd love to see a reproducible case. Thanks. |
I did have a release candidate of Go 1.6 installed at one point, so it's theoretically possible I had some libraries built with that version. Unfortunately I've since deleted |
I have reproduced this off of a fresh upgrade from 1.6.2 to 1.7. I do not believe that I have ever had an RC installed; go was previously installed with homebrew, and was installed this time with the official installer. I did My error log is this:
|
@dperny Thanks for the report. It may be possible to get this error when mixing packages using the old (textual) export format, and the new (binary) export format. The 1.7 compiler tries to be compatible to two export formats, and perhaps that's not a good idea. Maybe it should just flat-out reject packages using the old format. Then users would simply be prompted to recompile their packages. |
I started facing this issue now |
@dmportella Your comment on this closed issue is not actionable. If you see a new problem (with one of the 1.8 release candidates), please file a new issue with details so the problem can be reproduced. Thanks. |
@griesemer its oke I think after running
Everything started working |
Please answer these questions before submitting your issue. Thanks!
go version
)?go env
)?If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
The text was updated successfully, but these errors were encountered: