Revert of Set up a parallel memory.memory_health_quick_tbmv2 benchmark

Revert of Set up a parallel memory.memory_health_quick_tbmv2 benchmark (patchset #4 id:80001 of https://codereview.chromium.org/1907343002/ )

Reason for revert:
Broke data upload to perf dashboard for these benchmarks.

BUG=606698
Original issue's description:
> Set up a parallel memory.memory_health_quick_tbmv2 benchmark
>
> This patch adds a temporary parallel benchmark to compare the new TBMv2
> memory metric (third_party/catapult/tracing/tracing/metrics/
> system_health/memory_metric.html) with the existing TBMv1 one
> (third_party/catapult/telemetry/telemetry/web_perf/metrics/
> memory_timeline.py).
>
> Once all issues associated with the TBMv2 metric are resolved, all
> memory benchmarks will switch to use it instead of the TBMv1 metric and
> the temporary parallel benchmark will be removed.
>
> BUG=581716, 606361
> CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
>
> Committed: https://crrev.com/92efb5bc7f3830436cc047a39e79c5374b5a4d7a
> Cr-Commit-Position: refs/heads/master@{#389519}

TBR=primiano@chromium.org,nednguyen@google.com,petrcermak@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=581716, 606361
Committed: https://crrev.com/1c572b2ccff4c64f3e9aecd526729ffb4e89a00e
Cr-Commit-Position: refs/heads/master@{#389726}

[perezju, 2016-04-26 08:48:43]

Created Revert of Set up a parallel memory.memory_health_quick_tbmv2 benchmark

[commit-bot: I haz the power, 2016-04-26 08:48:58]

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

[commit-bot: I haz the power, 2016-04-26 08:49:26]

Description was changed from

==========
Revert of Set up a parallel memory.memory_health_quick_tbmv2 benchmark (patchset
#4 id:80001 of https://codereview.chromium.org/1907343002/ )

Reason for revert:
Broke data upload to perf dashboard for these benchmarks.

BUG=606698

Original issue's description:
> Set up a parallel memory.memory_health_quick_tbmv2 benchmark
> 
> This patch adds a temporary parallel benchmark to compare the new TBMv2
> memory metric (third_party/catapult/tracing/tracing/metrics/
> system_health/memory_metric.html) with the existing TBMv1 one
> (third_party/catapult/telemetry/telemetry/web_perf/metrics/
> memory_timeline.py).
> 
> Once all issues associated with the TBMv2 metric are resolved, all
> memory benchmarks will switch to use it instead of the TBMv1 metric and
> the temporary parallel benchmark will be removed.
> 
> BUG=581716,606361
>
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
> 
> Committed: https://crrev.com/92efb5bc7f3830436cc047a39e79c5374b5a4d7a
> Cr-Commit-Position: refs/heads/master@{#389519}

TBR=primiano@chromium.org,nednguyen@google.com,petrcermak@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=581716,606361
==========

to

==========
Revert of Set up a parallel memory.memory_health_quick_tbmv2 benchmark (patchset
#4 id:80001 of https://codereview.chromium.org/1907343002/ )

Reason for revert:
Broke data upload to perf dashboard for these benchmarks.

BUG=606698

Original issue's description:
> Set up a parallel memory.memory_health_quick_tbmv2 benchmark
> 
> This patch adds a temporary parallel benchmark to compare the new TBMv2
> memory metric (third_party/catapult/tracing/tracing/metrics/
> system_health/memory_metric.html) with the existing TBMv1 one
> (third_party/catapult/telemetry/telemetry/web_perf/metrics/
> memory_timeline.py).
> 
> Once all issues associated with the TBMv2 metric are resolved, all
> memory benchmarks will switch to use it instead of the TBMv1 metric and
> the temporary parallel benchmark will be removed.
> 
> BUG=581716,606361
>
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
> 
> Committed: https://crrev.com/92efb5bc7f3830436cc047a39e79c5374b5a4d7a
> Cr-Commit-Position: refs/heads/master@{#389519}

TBR=primiano@chromium.org,nednguyen@google.com,petrcermak@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=581716,606361
==========

[commit-bot: I haz the power, 2016-04-26 08:49:27]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-26 08:50:53]

Description was changed from

==========
Revert of Set up a parallel memory.memory_health_quick_tbmv2 benchmark (patchset
#4 id:80001 of https://codereview.chromium.org/1907343002/ )

Reason for revert:
Broke data upload to perf dashboard for these benchmarks.

BUG=606698

Original issue's description:
> Set up a parallel memory.memory_health_quick_tbmv2 benchmark
> 
> This patch adds a temporary parallel benchmark to compare the new TBMv2
> memory metric (third_party/catapult/tracing/tracing/metrics/
> system_health/memory_metric.html) with the existing TBMv1 one
> (third_party/catapult/telemetry/telemetry/web_perf/metrics/
> memory_timeline.py).
> 
> Once all issues associated with the TBMv2 metric are resolved, all
> memory benchmarks will switch to use it instead of the TBMv1 metric and
> the temporary parallel benchmark will be removed.
> 
> BUG=581716,606361
>
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
> 
> Committed: https://crrev.com/92efb5bc7f3830436cc047a39e79c5374b5a4d7a
> Cr-Commit-Position: refs/heads/master@{#389519}

TBR=primiano@chromium.org,nednguyen@google.com,petrcermak@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=581716,606361
==========

to

==========
Revert of Set up a parallel memory.memory_health_quick_tbmv2 benchmark (patchset
#4 id:80001 of https://codereview.chromium.org/1907343002/ )

Reason for revert:
Broke data upload to perf dashboard for these benchmarks.

BUG=606698

Original issue's description:
> Set up a parallel memory.memory_health_quick_tbmv2 benchmark
>
> This patch adds a temporary parallel benchmark to compare the new TBMv2
> memory metric (third_party/catapult/tracing/tracing/metrics/
> system_health/memory_metric.html) with the existing TBMv1 one
> (third_party/catapult/telemetry/telemetry/web_perf/metrics/
> memory_timeline.py).
>
> Once all issues associated with the TBMv2 metric are resolved, all
> memory benchmarks will switch to use it instead of the TBMv1 metric and
> the temporary parallel benchmark will be removed.
>
> BUG=581716,606361
>
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq
>
> Committed: https://crrev.com/92efb5bc7f3830436cc047a39e79c5374b5a4d7a
> Cr-Commit-Position: refs/heads/master@{#389519}

TBR=primiano@chromium.org,nednguyen@google.com,petrcermak@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=581716,606361

Committed: https://crrev.com/1c572b2ccff4c64f3e9aecd526729ffb4e89a00e
Cr-Commit-Position: refs/heads/master@{#389726}
==========

[commit-bot: I haz the power, 2016-04-26 08:50:54]

Patchset 1 (id:??) landed as
https://crrev.com/1c572b2ccff4c64f3e9aecd526729ffb4e89a00e
Cr-Commit-Position: refs/heads/master@{#389726}

[petrcermak, 2016-04-26 08:57:11]

lgtm

[nednguyen, 2016-04-27 17:04:31]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1920363003/ by nednguyen@google.com.

The reason for reverting is: Underlied problem should be already fixed.

 .