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

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}

[ssid, 2016-07-20 22:20:16]

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

[ssid, 2016-07-20 22:21:29]

Description was changed from

==========
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=513692
==========

to

==========
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
==========

[ssid, 2016-07-20 22:21:41]

Description was changed from

==========
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
==========

to

==========
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
==========

[ssid, 2016-07-20 22:22:02]

The CQ bit was checked by ssid@chromium.org

[commit-bot: I haz the power, 2016-07-20 22:22:54]

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-07-20 22:23:53]

Description was changed from

==========
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
==========

to

==========
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
==========

[commit-bot: I haz the power, 2016-07-20 22:23:54]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-20 22:26:18]

Description was changed from

==========
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
==========

to

==========
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}
==========

[commit-bot: I haz the power, 2016-07-20 22:26:19]

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

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

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

The reason for reverting is: Reference build was rolled, Issue 629987..

[Primiano Tucci (use gerrit), 2016-11-01 15:09:37]

On 2016/10/31 04:32:17, ssid wrote:
> A revert of this CL (patchset #1 id:1) has been created in
> https://codereview.chromium.org/2458413002/ by mailto:ssid@chromium.org.
> 
> The reason for reverting is: Reference build was rolled, Issue 629987..

Uh I got a bit lost here between revert and failed reland.
Any summary of what's the current state?

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

On 2016/11/01 15:09:37, Primiano Tucci wrote:
> On 2016/10/31 04:32:17, ssid wrote:
> > A revert of this CL (patchset #1 id:1) has been created in
> > https://codereview.chromium.org/2458413002/ by mailto:ssid@chromium.org.
> > 
> > The reason for reverting is: Reference build was rolled, Issue 629987..
> 
> Uh I got a bit lost here between revert and failed reland.
> Any summary of what's the current state?

I explained in https://codereview.chromium.org/2458413002#msg9.