You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.10 darwin/amd64
What did you do?
go test -v with some code that hangs.
What did you expect to see?
Logs.
What did you see instead?
Nothing. In the case where my code hangs forever, I don't get any test logs because logs are only printed in the success/fail case. Ctrl+C means I never get logs.
Furthermore, -v not showing logs means I get no sense of timing in test runs.
It's a real bummer to mass replace t.Log with fmt.Println, get my tests fixed, and then mass replace fmt.Println with t.Log.
The text was updated successfully, but these errors were encountered:
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.10 darwin/amd64
What did you do?
go test -v
with some code that hangs.What did you expect to see?
Logs.
What did you see instead?
Nothing. In the case where my code hangs forever, I don't get any test logs because logs are only printed in the success/fail case. Ctrl+C means I never get logs.
Furthermore,
-v
not showing logs means I get no sense of timing in test runs.It's a real bummer to mass replace t.Log with fmt.Println, get my tests fixed, and then mass replace fmt.Println with t.Log.
The text was updated successfully, but these errors were encountered: