We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With this benchmark:
package main import "testing" func BenchmarkLog(b *testing.B) { b.Log("why?") }
I get this output:
$ go test -bench . testing: warning: no tests to run PASS BenchmarkLog 2000000000 0.00 ns/op --- BENCH: BenchmarkLog issue_test.go:6: why? issue_test.go:6: why? issue_test.go:6: why? issue_test.go:6: why? issue_test.go:6: why? issue_test.go:6: why?
The docs say, "The text will be printed only if the test fails or the -test.v flag is set."
Why is b.Log logging anyway?
The text was updated successfully, but these errors were encountered:
I think this is a documentation issue. The code says:
// Unlike with tests, we ignore the -chatty flag and always print output for // benchmarks since the output generation time will skew the results.
Sorry, something went wrong.
e9827f6
Thanks guys. Great service!
No branches or pull requests
With this benchmark:
package main
import "testing"
func BenchmarkLog(b *testing.B) {
b.Log("why?")
}
I get this output:
$ go test -bench .
testing: warning: no tests to run
PASS
BenchmarkLog 2000000000 0.00 ns/op
--- BENCH: BenchmarkLog
issue_test.go:6: why?
issue_test.go:6: why?
issue_test.go:6: why?
issue_test.go:6: why?
issue_test.go:6: why?
issue_test.go:6: why?
The docs say, "The text will be printed only if the test fails or the -test.v flag is set."
Why is b.Log logging anyway?
The text was updated successfully, but these errors were encountered: