Reland of [telemetry] Trace config should be used to disable periodic dumps

Reland of [telemetry] Trace config should be used to disable periodic dumps (patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools "Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps (patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
>
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
>
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> > CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
>
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
>
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

Committed: https://crrev.com/813ee249f4aadce76998a6fc516fe7adccbb34be
Cr-Commit-Position: refs/heads/master@{#432846}

[ssid, 2016-10-31 04:32:18]

Created Reland of [telemetry] Trace config should be used to disable periodic
dumps

[ssid, 2016-10-31 04:32:35]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-31 04:32:42]

Dry run: 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-31 04:34:57]

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

[commit-bot: I haz the power, 2016-10-31 04:34:58]

Dry run: Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)

[ssid, 2016-11-03 07:51:31]

Description was changed from

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
==========

to

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[ssid, 2016-11-03 07:51:53]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-03 07:52:10]

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

[ssid, 2016-11-03 07:56:04]

landing this CL again so that we do not need enable-memory-benchmarking flag in
memory-infra. This was reverted because the old reference builds did not support
trace_config string via devtools Tracing.Start. Now, the reference build was
rolled (crbug.com/29987).

[ssid, 2016-11-03 08:01:26]

Description was changed from

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools
"Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[commit-bot: I haz the power, 2016-11-03 08:11:19]

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

[commit-bot: I haz the power, 2016-11-03 08:11:20]

Dry run: Try jobs failed on following builders:
  android_s5_perf_cq on master.tryserver.chromium.perf (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_...)

[nednguyen, 2016-11-03 10:06:03]

lgtm

[Primiano Tucci (use gerrit), 2016-11-03 13:33:55]

On 2016/11/03 10:06:03, nednguyen wrote:
> lgtm

thanks so much!

[ssid, 2016-11-04 09:43:34]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-04 09:43:49]

Dry run: 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-11-04 14:39:05]

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

[commit-bot: I haz the power, 2016-11-04 14:39:06]

Dry run: Try jobs failed on following builders:
  mac_retina_perf_cq on master.tryserver.chromium.perf (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_...)

[ssid, 2016-11-14 17:24:12]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-14 17:24:45]

Dry run: 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-11-14 19:27:45]

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

[commit-bot: I haz the power, 2016-11-14 19:27:46]

Dry run: Try jobs failed on following builders:
  android_s5_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build
URL)
  linux_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build URL)
  mac_retina_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build
URL)
  winx64_10_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build
URL)

[ssid, 2016-11-15 07:34:27]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-15 07:34:44]

Dry run: 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-11-15 09:35:13]

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

[commit-bot: I haz the power, 2016-11-15 09:35:14]

Dry run: Try jobs failed on following builders:
  android_s5_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build
URL)

[ssid, 2016-11-16 04:40:55]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-16 04:41:34]

Dry run: 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-11-16 06:42:38]

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

[commit-bot: I haz the power, 2016-11-16 06:42:39]

Dry run: Try jobs failed on following builders:
  android_s5_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build
URL)

[ssid, 2016-11-16 12:09:46]

Description was changed from

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools
"Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools
"Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[ssid, 2016-11-16 12:09:51]

The CQ bit was checked by ssid@chromium.org

[ssid, 2016-11-16 12:09:52]

The patchset sent to the CQ was uploaded after l-g-t-m from nednguyen@google.com
Link to the patchset: https://codereview.chromium.org/2458413002/#ps150001
(title: "Testing tot.")

[commit-bot: I haz the power, 2016-11-16 12:10:10]

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-11-16 14:52:12]

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

[commit-bot: I haz the power, 2016-11-16 14:52:13]

Try jobs failed on following builders:
  winx64_10_perf_cq on master.tryserver.chromium.perf (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_c...)

[ssid, 2016-11-17 06:05:55]

Patchset #3 (id:150001) has been deleted

[ssid, 2016-11-17 06:06:33]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-17 06:06:53]

Dry run: 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-11-17 11:28:02]

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

[commit-bot: I haz the power, 2016-11-17 11:28:03]

Dry run: This issue passed the CQ dry run.

[ssid, 2016-11-17 11:48:51]

The CQ bit was checked by ssid@chromium.org

[commit-bot: I haz the power, 2016-11-17 11:49:07]

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-11-17 11:53:04]

Description was changed from

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools
"Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools
"Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[commit-bot: I haz the power, 2016-11-17 11:53:05]

Committed patchset #2 (id:130001)

[commit-bot: I haz the power, 2016-11-17 11:55:04]

Description was changed from

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools
"Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
> 
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
> 
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
> 
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
> 
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
Reland of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2166833003/ )

Reason for revert:
Reference build was rolled, Issue 629987. Now reference build Devtools
"Tracing.Start" should support trace config string.

Original issue's description:
> Revert of [telemetry] Trace config should be used to disable periodic dumps
(patchset #1 id:1 of https://codereview.chromium.org/2162283002/ )
>
> Reason for revert:
> Looks like some reference builds still haven't got the devtools api update.
>
> Original issue's description:
> > [telemetry] Trace config should be used to disable periodic dumps
> >
> > Telemetry previously used the "--enable-memory-benchmarking" flag to
> > tell memory dump manager to disable periodic dumps. That is cleaned up
> > in this CL and the trace config is used to achieve this behavior.
> >
> > Note to perf sheriff: Memory benchmarks could regress if the config
> > did not propagate correctly.
> >
> > BUG=513692
> >
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq
> >
> > Committed: https://crrev.com/578e8ff55813d82c373563039f8ab4db28264ed6
> > Cr-Commit-Position: refs/heads/master@{#406598}
>
> TBR=nednguyen@google.com
> # Skipping CQ checks because original CL landed less than 1 days ago.
> NOPRESUBMIT=true
> NOTREECHECKS=true
> NOTRY=true
> BUG=629988, 513692
>
> Committed: https://crrev.com/aad3e5da6864138469892f1459137e19a0cd5e26
> Cr-Commit-Position: refs/heads/master@{#406691}

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=629988, 513692
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

Committed: https://crrev.com/813ee249f4aadce76998a6fc516fe7adccbb34be
Cr-Commit-Position: refs/heads/master@{#432846}
==========

[commit-bot: I haz the power, 2016-11-17 11:55:06]

Patchset 2 (id:??) landed as
https://crrev.com/813ee249f4aadce76998a6fc516fe7adccbb34be
Cr-Commit-Position: refs/heads/master@{#432846}