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
However, the bazel test --cache_test_results=no --test_output=all --test_arg="-test.v" does output the log lines to the test log. I'm surprised by that. I would have expected test_output=all (esp with -test.v) to put the output to stdout & stderr. Perhaps I'm wrong to be surprised by that, but as day-to-day Go hacker, I was.
What version of rules_go are you using?
0.50.1
What version of gazelle are you using?
0.39.1
What version of Bazel are you using?
7.3.1
Does this issue reproduce with the latest releases of all the above?
Yes.
What operating system and processor architecture are you using?
macOS arm
What did you do?
Tried to run all of the tests in a package without caching with verbosity turned up to see all of the
t.Logf
lines in it.I tried both with
-test.v
, andtest.count
and without:What did you expect to see?
All of the tests enumerated and all the log lines run by the tests like the usual
go test -v
command.Output like:
What did you see instead?
The versions with
-test.v
or-test.count
always just print (with--cache_test_results=no --test_output=all
included, of course) will only get you theDropping those and only run
bazel test --cache_test_results=no --test_output=all
will get you only:with the usual
after it
The text was updated successfully, but these errors were encountered: