We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please answer these questions before submitting your issue. Thanks!
go version
% go version go version devel +0dc814cd7f Sat Jun 30 01:04:30 2018 +0000 darwin/amd64
yes
go env
darwin/amd64
Daves-MacBook-Pro(~/src/github.com/heptio/contour/internal/dag) % go test # github.com/heptio/contour/internal/dag [github.com/heptio/contour/internal/dag.test] ./dag_test.go:2359:18: undefined: sevicemap ./dag_test.go:2446:18: undefined: sevicemap # github.com/heptio/contour/internal/dag ./dag_test.go:2359:18: undeclared name: sevicemap ./dag_test.go:2446:18: undeclared name: sevicemap vet: typecheck failures FAIL github.com/heptio/contour/internal/dag [build failed]
Daves-MacBook-Pro(~/src/github.com/heptio/contour/internal/dag) % go test # github.com/heptio/contour/internal/dag [github.com/heptio/contour/internal/dag.test] ./dag_test.go:2359:18: undefined: sevicemap ./dag_test.go:2446:18: undefined: sevicemap FAIL github.com/heptio/contour/internal/dag [build failed]
go test runs vet over the code that failed to compile causing it to report the same errors again with a slightly different prefix.
The text was updated successfully, but these errors were encountered:
Dup of #26125?
Sorry, something went wrong.
@myitcv whoops, sorry for the noise.
No branches or pull requests
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?darwin/amd64
What did you do?
What did you expect to see?
What did you see instead?
go test runs vet over the code that failed to compile causing it to report the same errors again with a slightly different prefix.
The text was updated successfully, but these errors were encountered: