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: do not buffer test output for 1-package test #2731

Closed
bradfitz opened this issue Jan 18, 2012 · 5 comments
Closed

cmd/go: do not buffer test output for 1-package test #2731

bradfitz opened this issue Jan 18, 2012 · 5 comments
Milestone

Comments

@bradfitz
Copy link
Contributor

go test's output buffering can be too aggressive.

For example,
 
go test -v net

... is testing a single package, so there's no need to buffer it to print its output
alphabetically by package.  I used to be able to "watch" the tests run with -v.
@dsymonds
Copy link
Contributor

Comment 1:

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

@rsc
Copy link
Contributor

rsc commented Jan 29, 2012

Comment 2:

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

Owner changed to @rsc.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Jan 30, 2012

Comment 3:

Labels changed: added go1-must.

@rsc
Copy link
Contributor

rsc commented Jan 31, 2012

Comment 4:

Status changed to Started.

@rsc
Copy link
Contributor

rsc commented Jan 31, 2012

Comment 5:

This issue was closed by revision 64a73b0.

Status changed to Fixed.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
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

4 participants