Panic stack trace from go test -timeout=X
is ignored when timeout happens right after a test passes
#292
Labels
go test -timeout=X
is ignored when timeout happens right after a test passes
#292
This seems like a bug in
go test -json
, so I've opened the following issue over there: golang/go#57305However, this is still relevant for
gotestsum
since previous Go versions are affected.The following visual should give an idea of what's wrong:
Something went wrong, but we simply don't know what. With parallel tests this is even more confusing:
The test fails with
(unknown)
, but no explanation.When this edge case isn't hit we see the proper output:
The json payloads are available at golang/go#57305, but for context, this is the significant portion:
What's going on here is that the test outputs
PASS
, relied on bygotestsum
to ignore future output from that test. However,go test
considers that test to be running still for a brief moment and attributes the panic stack trace to it.The text was updated successfully, but these errors were encountered: