Skip to content
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/trace: traces cannot convey time scale to Chrome viewer #10687

Closed
toffaletti opened this issue May 4, 2015 · 2 comments
Closed

cmd/trace: traces cannot convey time scale to Chrome viewer #10687

toffaletti opened this issue May 4, 2015 · 2 comments
Milestone

Comments

@toffaletti
Copy link

I recorded a trace with seconds=60s and in trace viewer the scale is 0-60000s. Before I noticed that I was drilling down into events and trying to reconcile 1,200 milliseconds to make a syscall.

I suspect this is from Go tracing reporting in nanoseconds, but trace viewer seems to be expecting microseconds.

@dvyukov

@dvyukov dvyukov added this to the Go1.5 milestone May 5, 2015
@dvyukov dvyukov self-assigned this May 5, 2015
@dvyukov
Copy link
Member

dvyukov commented May 5, 2015

Blocked on google/trace-viewer#624

@rsc rsc changed the title traces generated by pprof/trace have incorrect time scale in traceviewer runtime/pprof: traces cannot convey time scale to Chrome viewer Jun 17, 2015
@dvyukov
Copy link
Member

dvyukov commented Jul 19, 2015

@dvyukov dvyukov closed this as completed Jul 19, 2015
@mikioh mikioh changed the title runtime/pprof: traces cannot convey time scale to Chrome viewer cmd/trace: traces cannot convey time scale to Chrome viewer Jul 31, 2015
@golang golang locked and limited conversation to collaborators Aug 5, 2016
@rsc rsc unassigned dvyukov Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants