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

Jump to bottom

testing: an import cycle in a test file exposes an infinite loop in the go test command or the go cover tool #9031

Closed
gopherbot opened this issue Oct 30, 2014 · 2 comments
Closed

testing: an import cycle in a test file exposes an infinite loop in the go test command or the go cover tool #9031

gopherbot opened this issue Oct 30, 2014 · 2 comments
Labels
FrozenDueToAge

Comments

@gopherbot
Copy link

by mdwhatcott:

What does 'go version' print?

go version go1.3.3 darwin/amd64

What steps reproduce the problem?

1. go get github.com/mdwhatcott/cycle
2. cd $GOPATH/src/github.com/mdwhatcott/cycle
3. go test -cover

What happened? The go test command hangs indefinitely.

What should have happened instead? It should report a build failure due to an import
cycle.

Please provide any additional information below.

See the README.md file in the "github.com/mdwhatcott/cycle" package for more
details.

I understand that coverage information is only useful when the tests successfully
compile and execute, but in every other failure to compile, the command in step 3 above
reports the problem and exits with a non-zero return status. Why should an import cycle
not cause the same behavior?
@gopherbot
Copy link
Author

Comment 1 by mdwhatcott:

Well, just realized this is a duplicate of:
https://golang.org/issue/6872&q=go%20cover%20import%20cycle&colspec=ID%20Status%20Stars%20Release%20Owner%20Repo%20Summary
Sorry! Feel free to delete this issue, unless it provides any helpful information.

@ianlancetaylor
Copy link
Contributor

Comment 2:

Status changed to Duplicate.

Merged into issue #6872.

@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ianlancetaylor @gopherbot