Revert of Background tracing: Added config option for repeated trigger behavior

Revert of Background tracing: Added config option for repeated trigger behavior (patchset #1 id:1 of https://codereview.chromium.org/2247033005/ )

Reason for revert:
Test is flaky on builder "Android Tests"

Builder: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests

Failure:
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/30899

Output:
BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored (run #1):
[ RUN      ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored
[WARNING:dns_config_service_posix.cc(316)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(228)] Cannot start http server for devtools. Stop devtools.
../../content/browser/tracing/background_tracing_manager_browsertest.cc:1210: Failure
Value of: BackgroundTracingManagerImpl::GetInstance()->IsTracingForTesting()
  Actual: false
Expected: true
../../content/browser/tracing/background_tracing_manager_browsertest.cc:95: Failure
Value of: value
  Actual: true
Expected: expected
Which is: false
[  FAILED  ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored, where TypeParam =  and GetParam() =  (188 ms)
[----------] 1 test from BackgroundTracingManagerBrowserTest (188 ms total)

Original issue's description:
> Background tracing: Add config option to control whether or not to stop reactive tracing when a repeated trigger occurs
>
> R=simonhatch@chromium.org
> BUG=637129
>
> Committed: https://crrev.com/fba230c24383ae08ea6d924401bdff81b46c7108
> Cr-Commit-Position: refs/heads/master@{#412577}

TBR=simonhatch@chromium.org,ssid@chromium.org,petrcermak@chromium.org,oysteine@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=637129
Committed: https://crrev.com/ccb0f2af13bf3cc4ebdcdd7a08e19b281d788897
Cr-Commit-Position: refs/heads/master@{#413627}

[megjablon, 2016-08-23 00:09:05]

The CQ bit was checked by megjablon@chromium.org

[megjablon, 2016-08-23 00:09:05]

Created Revert of Background tracing: Added config option for repeated trigger
behavior

[commit-bot: I haz the power, 2016-08-23 00:10:28]

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-08-23 01:57:45]

Description was changed from

==========
Revert of Background tracing: Added config option for repeated trigger behavior
(patchset #1 id:1 of https://codereview.chromium.org/2247033005/ )

Reason for revert:
Test is flaky on builder "Android Tests"

Builder: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests

Failure:
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/3...

Output:
BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored (run #1):
[ RUN      ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored
[WARNING:dns_config_service_posix.cc(316)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(228)] Cannot start http server for devtools.
Stop devtools.
../../content/browser/tracing/background_tracing_manager_browsertest.cc:1210:
Failure
Value of: BackgroundTracingManagerImpl::GetInstance()->IsTracingForTesting()
  Actual: false
Expected: true
../../content/browser/tracing/background_tracing_manager_browsertest.cc:95:
Failure
Value of: value
  Actual: true
Expected: expected
Which is: false
[  FAILED  ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored,
where TypeParam =  and GetParam() =  (188 ms)
[----------] 1 test from BackgroundTracingManagerBrowserTest (188 ms total)

Original issue's description:
> Background tracing: Add config option to control whether or not to stop
reactive tracing when a repeated trigger occurs
> 
> R=simonhatch@chromium.org
> BUG=637129
> 
> Committed: https://crrev.com/fba230c24383ae08ea6d924401bdff81b46c7108
> Cr-Commit-Position: refs/heads/master@{#412577}

TBR=simonhatch@chromium.org,ssid@chromium.org,petrcermak@chromium.org,oystein...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=637129
==========

to

==========
Revert of Background tracing: Added config option for repeated trigger behavior
(patchset #1 id:1 of https://codereview.chromium.org/2247033005/ )

Reason for revert:
Test is flaky on builder "Android Tests"

Builder: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests

Failure:
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/3...

Output:
BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored (run #1):
[ RUN      ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored
[WARNING:dns_config_service_posix.cc(316)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(228)] Cannot start http server for devtools.
Stop devtools.
../../content/browser/tracing/background_tracing_manager_browsertest.cc:1210:
Failure
Value of: BackgroundTracingManagerImpl::GetInstance()->IsTracingForTesting()
  Actual: false
Expected: true
../../content/browser/tracing/background_tracing_manager_browsertest.cc:95:
Failure
Value of: value
  Actual: true
Expected: expected
Which is: false
[  FAILED  ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored,
where TypeParam =  and GetParam() =  (188 ms)
[----------] 1 test from BackgroundTracingManagerBrowserTest (188 ms total)

Original issue's description:
> Background tracing: Add config option to control whether or not to stop
reactive tracing when a repeated trigger occurs
> 
> R=simonhatch@chromium.org
> BUG=637129
> 
> Committed: https://crrev.com/fba230c24383ae08ea6d924401bdff81b46c7108
> Cr-Commit-Position: refs/heads/master@{#412577}

TBR=simonhatch@chromium.org,ssid@chromium.org,petrcermak@chromium.org,oystein...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=637129
==========

[commit-bot: I haz the power, 2016-08-23 01:57:47]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-23 01:59:34]

Description was changed from

==========
Revert of Background tracing: Added config option for repeated trigger behavior
(patchset #1 id:1 of https://codereview.chromium.org/2247033005/ )

Reason for revert:
Test is flaky on builder "Android Tests"

Builder: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests

Failure:
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/3...

Output:
BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored (run #1):
[ RUN      ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored
[WARNING:dns_config_service_posix.cc(316)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(228)] Cannot start http server for devtools.
Stop devtools.
../../content/browser/tracing/background_tracing_manager_browsertest.cc:1210:
Failure
Value of: BackgroundTracingManagerImpl::GetInstance()->IsTracingForTesting()
  Actual: false
Expected: true
../../content/browser/tracing/background_tracing_manager_browsertest.cc:95:
Failure
Value of: value
  Actual: true
Expected: expected
Which is: false
[  FAILED  ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored,
where TypeParam =  and GetParam() =  (188 ms)
[----------] 1 test from BackgroundTracingManagerBrowserTest (188 ms total)

Original issue's description:
> Background tracing: Add config option to control whether or not to stop
reactive tracing when a repeated trigger occurs
> 
> R=simonhatch@chromium.org
> BUG=637129
> 
> Committed: https://crrev.com/fba230c24383ae08ea6d924401bdff81b46c7108
> Cr-Commit-Position: refs/heads/master@{#412577}

TBR=simonhatch@chromium.org,ssid@chromium.org,petrcermak@chromium.org,oystein...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=637129
==========

to

==========
Revert of Background tracing: Added config option for repeated trigger behavior
(patchset #1 id:1 of https://codereview.chromium.org/2247033005/ )

Reason for revert:
Test is flaky on builder "Android Tests"

Builder: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests

Failure:
https://build.chromium.org/p/chromium.linux/builders/Android%20Tests/builds/3...

Output:
BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored (run #1):
[ RUN      ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored
[WARNING:dns_config_service_posix.cc(316)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(228)] Cannot start http server for devtools.
Stop devtools.
../../content/browser/tracing/background_tracing_manager_browsertest.cc:1210:
Failure
Value of: BackgroundTracingManagerImpl::GetInstance()->IsTracingForTesting()
  Actual: false
Expected: true
../../content/browser/tracing/background_tracing_manager_browsertest.cc:95:
Failure
Value of: value
  Actual: true
Expected: expected
Which is: false
[  FAILED  ] BackgroundTracingManagerBrowserTest.ReactiveSecondTriggerIgnored,
where TypeParam =  and GetParam() =  (188 ms)
[----------] 1 test from BackgroundTracingManagerBrowserTest (188 ms total)

Original issue's description:
> Background tracing: Add config option to control whether or not to stop
reactive tracing when a repeated trigger occurs
>
> R=simonhatch@chromium.org
> BUG=637129
>
> Committed: https://crrev.com/fba230c24383ae08ea6d924401bdff81b46c7108
> Cr-Commit-Position: refs/heads/master@{#412577}

TBR=simonhatch@chromium.org,ssid@chromium.org,petrcermak@chromium.org,oystein...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=637129

Committed: https://crrev.com/ccb0f2af13bf3cc4ebdcdd7a08e19b281d788897
Cr-Commit-Position: refs/heads/master@{#413627}
==========

[commit-bot: I haz the power, 2016-08-23 01:59:35]

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

[oystein (OOO til 10th of July), 2016-08-26 19:39:24]

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

The reason for reverting is: Re-landing with fix.