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: go test -i -c foo reports bar's errors twice #5679

Closed
alberts opened this issue Jun 11, 2013 · 4 comments
Closed

cmd/go: go test -i -c foo reports bar's errors twice #5679

alberts opened this issue Jun 11, 2013 · 4 comments
Milestone

Comments

@alberts
Copy link
Contributor

alberts commented Jun 11, 2013

What steps will reproduce the problem?

Make a package foo. Make a test in foo that imports a package bar. Add a compile error
to bar.

In your editor, make your build step:

go test -i -c foo

When this works, you know that your test is ready to run.

What is the expected output?

+ go test -i -c foo
# bar
src/bar/bar.go:3: undefined: net

What do you see instead?

+ go test -i -c foo
# bar
src/bar/bar.go:3: undefined: net
warning: building out-of-date packages:
    bar
installing these packages with 'go test -i foo' will speed future tests.

# bar
src/bar/bar.go:3: undefined: net

Which compiler are you using (5g, 6g, 8g, gccgo)?

6g

Which operating system are you using?

linux

Which version are you using?  (run 'go version')

go version devel +02e5cb24c95a Tue May 28 17:59:10 2013 -0700 linux/amd64

Please provide any additional information below.

Related to issue #3104 maybe.
@dvyukov
Copy link
Member

dvyukov commented Jun 11, 2013

Comment 1:

I would also like 'go test -i -c' to install and build at the same time.
I find it useful on underpowered laptops, where you can not afford to build twice.
Currently I do 'go test -i && go test -c'.

@davecheney
Copy link
Contributor

Comment 2:

Issue #5678 has been merged into this issue.

@rsc
Copy link
Contributor

rsc commented Jun 14, 2013

Comment 4:

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

Status changed to Accepted.

@robpike
Copy link
Contributor

robpike commented Aug 16, 2013

Comment 5:

This issue was closed by revision f0fef32.

Status changed to Fixed.

@rsc rsc added this to the Go1.2 milestone Apr 14, 2015
@rsc rsc removed the go1.2 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

6 participants