We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a go test fails, its output is not printed, difficulting the investigation of the problem.
For example the stacktrace of the failure in this build is only displayed as:
logger_test.go:43: logger_test.go:59:
The problem may be in the library we use to parse the output to generate the junit files:
beats/dev-tools/mage/gotest.go
Line 255 in df03add
Ideally we should be able to:
The text was updated successfully, but these errors were encountered:
Another example:
Sorry, something went wrong.
Maybe we can use gotestsum to fix this as explored here: #22541 Thanks @urso!
urso
Successfully merging a pull request may close this issue.
When a go test fails, its output is not printed, difficulting the investigation of the problem.
For example the stacktrace of the failure in this build is only displayed as:
The problem may be in the library we use to parse the output to generate the junit files:
beats/dev-tools/mage/gotest.go
Line 255 in df03add
Perhaps a different approach could be to do the parsing based on the JSON output of go test.
Ideally we should be able to:
The text was updated successfully, but these errors were encountered: