Skip to content
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: better document "go test" behavior on multiple packages #4576

Closed
gopherbot opened this issue Dec 20, 2012 · 2 comments
Closed

cmd/go: better document "go test" behavior on multiple packages #4576

gopherbot opened this issue Dec 20, 2012 · 2 comments
Milestone

Comments

@gopherbot
Copy link

by patrick.allen.higgins:

Running "go test pkg1 pkg2 pkg3" compiles and executes three separate test
binaries, one for each package. This behavior is implied by
http://golang.org/cmd/go/#hdr-Test_packages (particularly the -c flag docs imply the
package name is part of the binary) but is not explicit.

A "go test -x pkg1 pkg2 pkg3" makes the current behavior clear, but it's not
clear if this behavior is intentionally undefined.

Original discussion on golang-nuts:
https://groups.google.com/forum/?fromgroups=#!topic/golang-nuts/ta_LwdPrKwU
@rsc
Copy link
Contributor

rsc commented Dec 30, 2012

Comment 2:

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Jan 31, 2013

Comment 3:

This issue was closed by revision 8b6534b.

Status changed to Fixed.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants