|tagger||Simon <email@example.com>||Tue Jul 07 15:49:19 2015|
|author||Simon <firstname.lastname@example.org>||Mon Jul 06 20:07:14 2015|
|committer||Simon <email@example.com>||Mon Jul 06 20:07:14 2015|
Choose default trace name based on client. The XHR client produces compressed traces, while the inspector doesn't. This is causing problems when capturing a trace from android devices, saving it, then loading the saved trace since the file is named with .gz but the contents aren't actually compressed. BUG=1087 Rfirstname.lastname@example.org Review URL: https://codereview.appspot.com/252070043.
It provides rich analysis and visualization capabilities for many types of trace files. Its particularly good at viewing linux kernel traces (aka ftrace) and Chrome's trace_event format. Trace viewer can be embedded as a component in your own code, or used from a plain checkout to turn trace files into standalone, emailable HTML files from the commandline:
./tracing/trace2html my_trace.json --output=my_trace.html && open my_trace.html
Its easy to extend trace viewer to support your favorite trace format, or add domain specific visualizations to the UI to simplify drilling down into complex data.
We welcome contributions! To hack on this code, from toplevel: ./tracing/run_dev_server
In any browser, navigate to http://localhost:8003/
To run all python unittests: ./tracing/run_py_tests
To run all tracing unittests in d8 environment: ./tracing/run_d8_tests
To run all the unittests, you can also do:
Join our Google Groups: