Daniel Nephin

Thank you for the bug report! I ran this example with `go test -json -bench=.` to see what `test2json` output was received by `gotestsum`. The output looks something like this:...

Extracting to a directory named with the run-id is what I was expecting. Leaving the files zipped could also work, but is a little more work to deal with.

This is the current example usage for the command: https://github.com/cli/cli/blob/3b2397811400a6bc5d98f9e66cd95d34c377bb0e/pkg/cmd/run/download/download.go#L55-L65 From my perspective the current behaviour of `-n` without a run-id is broken. It doesn't behave as documented, but it's...

Thank you for the bug report! `--hide-summary` fixing the issue is surprising! `gotestsum` only runs as a single process and goroutine. The exit code from `go test` should always be...

Could you share the output with `--debug` ? Since this is running with `--format=pkgname` it's not clear to me if those failures were intermediate failures, or failures from the last...

I looked at the output and it seems correct to me. The first run failed 3 tests, the second run failed no new tests (only the same 3 failures from...

I think there may be some misunderstanding about how this works. Let me try to explain. 1. `gotestsum` runs all the tests 2. Re-run any test that failed in step...

Thanks for the bug report! This is unfortunately a common problem with `go test -json` (which `gotestsum` reads). The issue tracking that problem is https://github.com/golang/go/issues/26325. It looks like it was...

Thank you for the feature suggestion! Job summaries ([docs](https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)) seem like a great feature. It looks like these summaries are printed separately from the test output, so the way I...

Hello, try ``` gotestsum --junitfile unit-tests1.xml -- -run '^Test1$|Test11$' ```