-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/test2json: missing pass/fail action on individual benchmark #61767
Comments
This might be working-as-intended. Consider the output of
and
Notice how there's no "PASS" printed for the benchmark itself, only the summary "PASS" at the end. On the other hand, maybe that was a mistake, and it can be fixed in the json case. cc @bcmills also. |
Hey David! This is why I left the breadcrumb of https://go-review.googlesource.com/c/go/+/443596. That CL intentionally introduces the behavior that when Try this:
|
gotestsum can't properly process benchmark results due to a go toolchain bug. Remove the postprocessing, since we don't benefit as much now that we don't use Semaphore CI anymore (which had nice visualisation for JUnit output). See golang/go#61767 Signed-off-by: Lorenz Bauer <lmb@isovalent.com>
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?Not relevant - omitting
What did you do?
File
foo_test.go
:Run
go test -json -bench=. foo_test.go
Result:
What did you expect to see?
Note that TestFoo gets a line with an individual test result --
This is missing for BenchmarkFib10.
Expected to see:
After Fib10 passes.
Really, this likely means that BenchmarkFib10 needs to be framed with a
--- (PASS|SKIP|FAIL): BenchmarkFib10 (0.00s)\n
at the end when-test.v=test2json
is passed to the test binary as well.(Previous work in this area fixed most of the test2json issues I've seen, cc @rsc -- https://go-review.googlesource.com/c/go/+/443596)
The text was updated successfully, but these errors were encountered: