gotestsum reports nonexistent errors

[fgm]

Here is the situation: tests succeed with go test, both on their own and in the embedded go test -json command for gotestsum, but when gotestsum is done, it reports one error where none exists; and what's more it returns with status 0.

# Testing with gotestsum
./bin/gotestsum -f standard-verbose -- -v -count=1 -race ./somepackage
# github.com/someorg/somepackage/some.test
=== RUN   TestFoo
=== RUN   TestFoo/bar
--- PASS: TestFoo (0.00s)
    --- PASS: TestFoo/bar (0.00s)
PASS
ok  	github.com/someorg/somepackage	2.586s

=== Errors

DONE 2 tests, 1 error in 4.981s

$ echo $?
0

# Testing with go test
$ go test                              -v -count=1 -race ./somepackage 
# github.com/someorg/somepackage/some.test
=== RUN   TestFoo
=== RUN   TestFoo/bar
--- PASS: TestFoo (0.00s)
    --- PASS: TestFoo/bar (0.00s)
PASS
ok  	github.com/someorg/somepackage	1.636s

$ echo $?
0

Tested on

• macOS Sonoma, Apple Silicon.
• Both with go 1.22.6 and 1.23.0.
• gotestsum version dev

[dnephin]

Hello, thank you for the bug report! Errors come from any stderr that is emitted from the test binary. I don't see any lines in this example. Do you have some code I can run to reproduce?

[ikari-pl]

I have a similar problem. Even the junit.xml starts with

<?xml version="1.0" encoding="UTF-8"?>
<testsuites tests="6412" failures="0" errors="1" time="412.795940">

but I literally can't find any error, failure, stack, NOTHING that could have gone wrong in the logs, or the report.

[dnephin]

@ikari-pl what version of gotestsum ? Does it happen every time, or occasionally?

This can happen when go test -json writes something to stderr. In this case it seems like it's writing an empty line, which is strange.

I guess we can fix this by adding something here that ignores blank lines.

if strings.TrimSpace(line) == "" {
    continue
}

If someone wants to submit a PR, I can approve it.