Aha, now I understand. I managed to reproduce the problem and the failure was occurring while running go vet after the build target (which runs go build on all our packages). Switching to go install to build the packages cleared the problem right up.
On Thu, 15 Sep 2016 at 20:19 Dave Cheney <d...@cheney.net> wrote: > I don't think it's about the installation of the tools. The problem you've > described sounds like you have tools that use the compiled form of the > package, but your development process has not embraced go install so what > you go build the later test is not the same thing. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/fn_wmxgphSI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Twitter: @theotherelliott Blog: http://telliott.io Come work with us at Yext! http://grnh.se/ovuj20 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
