summaryrefslogtreecommitdiffstats
path: root/dbus/test_server.cc
diff options
context:
space:
mode:
authorsullivan <sullivan@chromium.org>2014-12-22 15:46:07 -0800
committerCommit bot <commit-bot@chromium.org>2014-12-22 23:46:56 +0000
commitfdb146cf261d909613a1d1b11e70d0ba96280ffe (patch)
tree0a7179670efcca99df2705177ce42bdb390f6a3b /dbus/test_server.cc
parent0db63a93861584f18f5dba98ad1bd5e67abc196d (diff)
downloadchromium_src-fdb146cf261d909613a1d1b11e70d0ba96280ffe.zip
chromium_src-fdb146cf261d909613a1d1b11e70d0ba96280ffe.tar.gz
chromium_src-fdb146cf261d909613a1d1b11e70d0ba96280ffe.tar.bz2
Implement ubertracing.
This is based on Nat's patch: https://codereview.chromium.org/441873007/ Move timeline and importers to use telemetry.timeline.TraceData This (admittedly massive) patch actually gives us an ubertrace object: the TraceData. The key way to understand this CL is to read timeline/trace_data.py file, then read importer.py. The rest is cosmetic fallout from the signature changes. A TraceData contains the data from many tracers, and is always serializable. A TimelineModel is constructed from a single TraceData. Internally, a TraceData is an in memory version of json of the following form: { traceEvents: ... inspectorTimelineEvnets: ... tabIds: ... } Since a TraceData has all the tracer data, the model and importer system was updated so that instead of there being 1 importer per value, the importers instead indicate which part of the TraceData they can handle, if any. BUG=356763 Review URL: https://codereview.chromium.org/805463002 Cr-Commit-Position: refs/heads/master@{#309489}
Diffstat (limited to 'dbus/test_server.cc')
0 files changed, 0 insertions, 0 deletions