-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: -json test report ordering #28953
Labels
GoCommand
cmd/go
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Comments
@sagikazarmark do you know if this is modules-specific? |
Haven't tried, but can be easily tested by cloning the repo into GOPATH. I'd be surprised though if it would be. |
|
As far as I can tell, this still occurs on Go 1.15:
|
Is this still happening? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
GoCommand
cmd/go
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I ran tests for a module using the following commands:
Repository: https://github.com/reproduce/golant-test-ordering-issue
What did you expect to see?
I expected to see the test events to be in the exact same order in each case
What did you see instead?
go test -v ./...
Outputgo test -v -json ./...
Outputgo test -v ./... | go tool test2json
OutputAs per https://golang.org/cmd/test2json I expect to see the events to be in the exact same order:
But they are not. This causes a problem when one would like to get a json output for some kind of reporting purpose, but still want to display the regular test report to the user.
The text was updated successfully, but these errors were encountered: