-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
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
cmd/go: 'go test all' tests unused std lib packages when using modules #31075
Labels
FrozenDueToAge
modules
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Comments
alexedwards
changed the title
cmd/go: go test all
cmd/go: go test all testing unused std lib packages
Mar 27, 2019
alexedwards
changed the title
cmd/go: go test all testing unused std lib packages
cmd/go: 'go test all' tests unused std lib packages
Mar 27, 2019
alexedwards
changed the title
cmd/go: 'go test all' tests unused std lib packages
cmd/go: 'go test all' tests unused std lib packages whne using modules
Mar 27, 2019
alexedwards
changed the title
cmd/go: 'go test all' tests unused std lib packages whne using modules
cmd/go: 'go test all' tests unused std lib packages when using modules
Mar 27, 2019
Note from the “system details” section of the report:
That indicates that the |
bcmills
added
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
modules
labels
Mar 27, 2019
CC @jayconrod
|
Ah, I see. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
modules
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Based on #26317 (comment) and the documentation for
all
ingo help packages
, when using modules I expectgo test all
to test only the standard library packages which actually get built into the packages in a module.It appears to be testing all standard library packages.
System details
What did you do?
What did you expect to see?
From
go help packages
:So I would expect to see
go test all
test the following standard library packages only (based on the output ofgo list -deps
):What did you see instead?
Running
go test all
appears to unnecessarily test additional standard library packages:The text was updated successfully, but these errors were encountered: