[v8 runtime stats] Migrate the runtime stats mapper to use the runtime stats metric instead

[v8 runtime stats] Migrate the runtime stats mapper to use the runtime stats metric instead

This experimental mapper was faling due to changes in the value system.
Now that we have a corresponding metric, I am migrating it to use
that metric instead which will help with reducing maintainence on that
mapper in the future.

TBR=eakuefner@chromium.org,benjhayden@chromium.org

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

[fmeawad, 2016-10-28 17:51:57]

Description was changed from

==========
[v8 runtime stats] Migrate the runtime stats mapper to use the runtime stats
metric instead

This experimental mapper was faling due to changes in the value system.
Now that we have a corresponding metric, I am migrating it to use
that metric instead which will help with reducing maintainence on that
mapper in the future.

TBR=eakuefner@chromium.org,benjhayden@chromium.org
==========

to

==========
[v8 runtime stats] Migrate the runtime stats mapper to use the runtime stats
metric instead

This experimental mapper was faling due to changes in the value system.
Now that we have a corresponding metric, I am migrating it to use
that metric instead which will help with reducing maintainence on that
mapper in the future.

TBR=eakuefner@chromium.org,benjhayden@chromium.org
==========

[fmeawad, 2016-10-28 17:52:01]

The CQ bit was checked by fmeawad@chromium.org

[commit-bot: I haz the power, 2016-10-28 17:52:12]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-28 18:16:57]

Description was changed from

==========
[v8 runtime stats] Migrate the runtime stats mapper to use the runtime stats
metric instead

This experimental mapper was faling due to changes in the value system.
Now that we have a corresponding metric, I am migrating it to use
that metric instead which will help with reducing maintainence on that
mapper in the future.

TBR=eakuefner@chromium.org,benjhayden@chromium.org
==========

to

==========
[v8 runtime stats] Migrate the runtime stats mapper to use the runtime stats
metric instead

This experimental mapper was faling due to changes in the value system.
Now that we have a corresponding metric, I am migrating it to use
that metric instead which will help with reducing maintainence on that
mapper in the future.

TBR=eakuefner@chromium.org,benjhayden@chromium.org

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

[commit-bot: I haz the power, 2016-10-28 18:16:58]

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

[eakuefner, 2016-10-28 18:21:20]

Why do you need the mapper at all any more? Can it be deleted? It seems like
you're essentially just passing through the results of the metric. It's not
necessary to have a mapper just to work with trace processor; metric support is
built-in.

[fmeawad, 2016-10-28 18:31:37]

On 2016/10/28 18:21:20, eakuefner wrote:
> Why do you need the mapper at all any more? Can it be deleted? It seems like
> you're essentially just passing through the results of the metric. It's not
> necessary to have a mapper just to work with trace processor; metric support
is
> built-in.

I need the mapper to change the format of the result to fit the rest of the
experiment
I am running. The experiment will run for another 2 weeks, and it is easier for
me
to maintain the current pipeline as is for now. Once the experiment is over, I
will delete
the related files.