cmd/vet: reports different results on different computers #21551
Labels
Comments
Are you positive it's not a duplicate of the issue above? Could you provide a way to reproduce the program? A self-contained program or set of packages would be best. Does this happen with 1.9rc2? |
The problem seems to be related to differences in how the normal compilation and running on programs handle paths, compared to Running Running Interestingly enough, without verbose, it fails silently with exit code 0. |
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
)?Both people use
go version go1.8.3 darwin/amd64
.Does this issue reproduce with the latest release?
Later versions show new/different results, but they are still not consistent across different computers.
What operating system and processor architecture are you using (
go env
)?Only difference on the other machine is
GOPATH="/Users/uwe/dev/go"
.What did you do?
Initialize a struct with multiple keys. Without explicitly specifying each key, but instead relying on the ordering. This would constitute a linter error with certain linter settings.
What did you expect to see?
Same linter output on each computer, so
Composite literal uses unkeyed fields
.What did you see instead?
The linter error appears on the computer with,
GOPATH=$HOME/dev/go
but not on the one withGOPATH=$HOME/go
.(I don't think necessarily it's related to the GOPATH. Consider it just an identifier for the different computers in this case.)
Related tickets
#12636
The text was updated successfully, but these errors were encountered: