cmd/vet: panics #17258
Closed
cmd/vet: panics #17258
Labels
Comments
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.7.1 darwin/amd64
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/mgalkowski/work/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.1/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/cs/93b4_xbx4l5gn1wx0f69p3d40000gn/T/go-build080226465=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
What did you do?
i did run
go vet ./...
in my project base dir. I did get a lot of panics.I did rerun it with
go vet -x ./...
and found that vet would panic checking seemingly correct packages. The whole project is building and running correctlyWhat did you expect to see?
No panics
What did you see instead?
Panics.
Our repo is private, so I can't share the code here, but i did run go vet also in our vendor dir. I did get this :
jose2go is vendored at the 2a04a552f4a8adf7d51731877b7a2021bab968bb commit.
This part
does vary from package to package. Sometimes it is :
or
I will try to produce a minimal repro.
The text was updated successfully, but these errors were encountered: