Trace-Viewer is the javascript frontend for Chrome about:tracing and Android systrace.
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:
$CATAPULT/tracing/bin/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.
There are two type of tests.
Run http server $CATAPULT/bin/run_dev_server. In any browser, navigate to http://localhost:8003/
| Unit tests | Descripton |
|---|---|
| All tests | http://localhost:8003/tests.html |
| All tests with short format | http://localhost:8003/tracing/tests.html?shortFormat |
| An individual test suite(such as ui/foo_test.js) | http://localhost:8003/tests.html?testSuiteName=ui.foo |
| Tests named foo | http://localhost:8003/tests.html?testFilterString=foo |
| Unit tests | Description |
|---|---|
| All python tests | $CATAPULT/tracing/bin/run_py_tests |
| All tracing tests in d8 environment | $CATAPULT/tracing/bin/run_vinn_tests |
| All tracing tests in devserver environment | $CATAPULT/tracing/bin/run_devserver_tests |
| All tests | $CATAPULT/tracing/bin/run_tests |
Make sure tests pass before sending us changelist. We use Gerrit for codereview. For more details, esp on Gerrit, read our contributing guide or check out the Getting Started guide.
Join our Google Group: