Make trace_event_importer recognize timing conversion and parse web user timing events

Make trace_event_importer recognize timing conversion and parse web user timing
events into nested slices

User timing slices are created using Timing.mark(GroupName, TaskName, opt_args),
they have the convention of

GroupName:TaskName/opt_args

where GroupName is used to group slices into a single track with hierarchical
structure, opt_args is optional arguments which are parsed into base64 string.

For more details, see the design doc:

https://docs.google.com/document/d/1-44PszmhQ0-M6Sf2dZpVu-9jAOa7w2_vKAKckRWXJms/edit?usp=sharing

BUG=catapult:#1880

Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/56ebb1bdfc67d48a5549f012edd56994a0cdbbfc

[lpy, 2016-01-08 22:35:33]

lpy@chromium.org changed reviewers:
+ fmeawad@chromium.org, nduca@chromium.org

[lpy, 2016-01-08 22:35:34]

ptal

[nduca, 2016-01-11 17:22:18]

your cl description isn't very clear. i think you should improve it a bit.

"Make trace_event_importer to parse nested web user timing events.

Detailed description of what web user timing events look like

Link to design doc.

BUG="

https://codereview.chromium.org/1573643002/diff/20001/tracing/tracing/extras/...
File tracing/tracing/extras/importer/trace_event_importer_test.html (right):

https://codereview.chromium.org/1573643002/diff/20001/tracing/tracing/extras/...
tracing/tracing/extras/importer/trace_event_importer_test.html:5200: 
you probably should have a test that has mixed non-user-timing and user timing
events... how do we know that a trace with both still parses well?

[lpy, 2016-01-11 17:56:30]

Description was changed from

==========
Make trace_event_importer recognize timing conversion

BUG=catapult:#1880
==========

to

==========
Make trace_event_importer recognize timing conversion and parse web user timing
events into nested slices

User timing slices are created using Timing.mark(GroupName, TaskName, opt_args),
they have the convention of

GroupName:TaskName/opt_args

where GroupName is used to group slices into a single track with hierarchical
structure, opt_args is optional arguments which are parsed into base64 string.

For more details, see the design doc:

https://docs.google.com/document/d/1-44PszmhQ0-M6Sf2dZpVu-9jAOa7w2_vKAKckRWXJ...

BUG=catapult:#1880
==========

[lpy, 2016-01-11 18:56:40]

ptal

https://codereview.chromium.org/1573643002/diff/20001/tracing/tracing/extras/...
File tracing/tracing/extras/importer/trace_event_importer_test.html (right):

https://codereview.chromium.org/1573643002/diff/20001/tracing/tracing/extras/...
tracing/tracing/extras/importer/trace_event_importer_test.html:5200: 
On 2016/01/11 17:22:18, nduca wrote:
> you probably should have a test that has mixed non-user-timing and user timing
> events... how do we know that a trace with both still parses well?

Done.

[nduca, 2016-01-11 19:30:43]

lgtm

[lpy, 2016-01-11 21:13:50]

The CQ bit was checked by lpy@chromium.org

[commit-bot: I haz the power, 2016-01-11 21:14:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1573643002/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1573643002/40001

[commit-bot: I haz the power, 2016-01-11 21:24:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-11 21:24:21]

Try jobs failed on following builders:
  Catapult Linux Tryserver on master.tryserver.client.catapult (JOB_FAILED,
https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Li...)

[lpy, 2016-01-11 21:34:27]

The CQ bit was checked by lpy@chromium.org

[lpy, 2016-01-11 21:34:27]

The patchset sent to the CQ was uploaded after l-g-t-m from nduca@chromium.org
Link to the patchset: https://codereview.chromium.org/1573643002/#ps60001
(title: "Skip create nestable async slices in D8 test")

[commit-bot: I haz the power, 2016-01-11 21:34:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1573643002/60001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1573643002/60001

[commit-bot: I haz the power, 2016-01-11 21:45:07]

Description was changed from

==========
Make trace_event_importer recognize timing conversion and parse web user timing
events into nested slices

User timing slices are created using Timing.mark(GroupName, TaskName, opt_args),
they have the convention of

GroupName:TaskName/opt_args

where GroupName is used to group slices into a single track with hierarchical
structure, opt_args is optional arguments which are parsed into base64 string.

For more details, see the design doc:

https://docs.google.com/document/d/1-44PszmhQ0-M6Sf2dZpVu-9jAOa7w2_vKAKckRWXJ...

BUG=catapult:#1880
==========

to

==========
Make trace_event_importer recognize timing conversion and parse web user timing
events into nested slices

User timing slices are created using Timing.mark(GroupName, TaskName, opt_args),
they have the convention of

GroupName:TaskName/opt_args

where GroupName is used to group slices into a single track with hierarchical
structure, opt_args is optional arguments which are parsed into base64 string.

For more details, see the design doc:

https://docs.google.com/document/d/1-44PszmhQ0-M6Sf2dZpVu-9jAOa7w2_vKAKckRWXJ...

BUG=catapult:#1880

Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2016-01-11 21:45:08]

Committed patchset #4 (id:60001) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...