cmd/go: rethink 'go get' skipping test-only packages #20760
Labels
FrozenDueToAge
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
Issue #15093 complained that go get x.com/y/... can match (via the wildcard) a directory x.com/y/z that only has tests in it, and then the 'go get' fails, because it cannot run 'go install x.com/y/z'. A fix was made for that CL, which silences the reporting of the "no Go files" error in x.com/y/z during 'go get', provided there are test files in that directory.
That fixes the problem reported, but it introduces other problems:
A pending CL of mine will address 3 and 4; we should reconsider 1 and 2 at some later point.
The text was updated successfully, but these errors were encountered: