Binary-only package leads to vet config not found error

The go version is 1.11
In order to achieve binary code sharing, I used the binary-only package like this:

After that, the binary (.a files) can successfully share to another project B, go build is fine and can get the output. However, if I run go test for project B, it exits with code 1. The error print is “vet config not found”. After investigation, go test execute go vet automatically, and I am not sure why go vet return exit code 1.

If I use the -vet=off flag, go test skips the go vet checking and every thing is fine but I don’t want to skip it.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.