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
go help testflag does not mention the -trace flag
The output of go tool trace -help is unhelpful:
Usage of 'go tool trace': Given a trace file produced by 'go test': go test -trace=trace.out pkg
Open a web browser displaying trace: go tool trace [flags] pkg.test trace.out
Flags: -http=addr: HTTP service address (e.g., ':6060')
Also, shortly after the 1.5 release, there should be a blog post about the feature.
The text was updated successfully, but these errors were encountered:
go help testflag does mention the -trace flag I've tried to describe -trace everywhere where cpu and memory profiles are described.
go tool trace -help is roughly the same as to tool cover -help, except that trace has fewer flags than cover.
Is there anything else to fix?
Sorry, something went wrong.
I think it's all good now.
Is there still plans to do a blog post on the trace tool? There's not much documentation on how to read the output from go tool trace.
go tool trace
@prashantv Do you mean the generated HTMLs? There are still plans to write the blog, not nobody is actively working on this ATM.
Yes, the generated HTML / SVGs. Hope to see the blog post soon!
No branches or pull requests
go help testflag does not mention the -trace flag
The output of go tool trace -help is unhelpful:
Usage of 'go tool trace':
Given a trace file produced by 'go test':
go test -trace=trace.out pkg
Open a web browser displaying trace:
go tool trace [flags] pkg.test trace.out
Flags:
-http=addr: HTTP service address (e.g., ':6060')
Also, shortly after the 1.5 release, there should be a blog post about the feature.
The text was updated successfully, but these errors were encountered: