It looks like ginkgo always invokes Go test binaries with -test.v.

I think this is the code line where this is decided:

Should that perhaps only be added when running ginkgo -v?

I want to to use ginkgo as main test runner because then I can parallelize my rather large Ginkgo test suite while running some smaller, normal Go tests sequentially (but ideally, those would also run in parallel, see #280). Because output is large, I only want to see it when a test fails. I'm almost there, except for the -test.v...