Revert of Plumb activation time to main

Revert of Plumb activation time to main (patchset #16 id:280001 of https://codereview.chromium.org/2778223005/ )

Reason for revert:
Failure observed in LayerTreeHostProxyTestActivationTime.RunMultiThread_DelegatingRenderer

https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.win%2FWin7_Tests__dbg__1_%2F59244%2F%2B%2Frecipes%2Fsteps%2Fcc_unittests%2F0%2Flogs%2FLayerTreeHostProxyTestActivationTime.RunMultiThread_DelegatingRenderer%2F0


Original issue's description:
> Plumb activation time in cc to Blink Scheduler in Main
> 
> BUG=657826, 657825
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2778223005
> Cr-Commit-Position: refs/heads/master@{#465701}
> Committed: https://chromium.googlesource.com/chromium/src/+/9a2eb472fde51de48c095c9c208101c534ac211e

TBR=brianderson@chromium.org,ccameron@chromium.org,alexclarke@chromium.org,miguelg@chromium.org,tedchoc@chromium.org,panicker@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=657826, 657825
Review-Url: https://codereview.chromium.org/2833603002
Cr-Commit-Position: refs/heads/master@{#465757}
Committed: https://chromium.googlesource.com/chromium/src/+/8aeea939c0f289b85181b6e8fc9c0966451e9369

[Roger McFarlane (Chromium), 2017-04-19 21:21:12]

The CQ bit was checked by rogerm@chromium.org

[Roger McFarlane (Chromium), 2017-04-19 21:21:13]

Created Revert of Plumb activation time to main

[commit-bot: I haz the power, 2017-04-19 21:22:02]

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

[panicker, 2017-04-19 21:26:42]

LGTM.
For the roll forward, could you indicate how to run the failing test? 
Is it flaky or failing consistently? Did it run on Presubmit?
Thanks!

[commit-bot: I haz the power, 2017-04-19 21:27:01]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492636872669940, "parent_rev":
"3c1e950bab1695de7e24a75b8ed5d6c413bf949a", "commit_rev":
"8aeea939c0f289b85181b6e8fc9c0966451e9369"}

[commit-bot: I haz the power, 2017-04-19 21:27:14]

Description was changed from

==========
Revert of Plumb activation time to main (patchset #16 id:280001 of
https://codereview.chromium.org/2778223005/ )

Reason for revert:
Failure observed in
LayerTreeHostProxyTestActivationTime.RunMultiThread_DelegatingRenderer

https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.win%2FWin7_Test...


Original issue's description:
> Plumb activation time in cc to Blink Scheduler in Main
> 
> BUG=657826,657825
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2778223005
> Cr-Commit-Position: refs/heads/master@{#465701}
> Committed:
https://chromium.googlesource.com/chromium/src/+/9a2eb472fde51de48c095c9c2081...

TBR=brianderson@chromium.org,ccameron@chromium.org,alexclarke@chromium.org,mi...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=657826,657825
==========

to

==========
Revert of Plumb activation time to main (patchset #16 id:280001 of
https://codereview.chromium.org/2778223005/ )

Reason for revert:
Failure observed in
LayerTreeHostProxyTestActivationTime.RunMultiThread_DelegatingRenderer

https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.win%2FWin7_Test...


Original issue's description:
> Plumb activation time in cc to Blink Scheduler in Main
> 
> BUG=657826,657825
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
> 
> Review-Url: https://codereview.chromium.org/2778223005
> Cr-Commit-Position: refs/heads/master@{#465701}
> Committed:
https://chromium.googlesource.com/chromium/src/+/9a2eb472fde51de48c095c9c2081...

TBR=brianderson@chromium.org,ccameron@chromium.org,alexclarke@chromium.org,mi...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=657826,657825

Review-Url: https://codereview.chromium.org/2833603002
Cr-Commit-Position: refs/heads/master@{#465757}
Committed:
https://chromium.googlesource.com/chromium/src/+/8aeea939c0f289b85181b6e8fc9c...
==========

[commit-bot: I haz the power, 2017-04-19 21:27:15]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/8aeea939c0f289b85181b6e8fc9c...

[ojan, 2017-04-19 21:45:48]

ojan@chromium.org changed reviewers:
+ ojan@chromium.org

[ojan, 2017-04-19 21:45:48]

Here's the first failing run. It failed twice in a row, so it's probably not
flaky, but hard to be 100% sure.

https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%2...

[Roger McFarlane (Chromium), 2017-04-19 21:47:39]

On 2017/04/19 21:26:42, panicker wrote:
> LGTM.
> For the roll forward, could you indicate how to run the failing test? 
> Is it flaky or failing consistently? Did it run on Presubmit?
> Thanks!

this should do the trick...

cc_unittests
--gtest_filter=LayerTreeHostProxyTestActivationTime.RunMultiThread_DelegatingRenderer

That runs only the test that failed.

The command on the bot that ran the entire suite was:

cc_unittests.exe --brave-new-test-launcher --test-launcher-bot-mode
--test-launcher-summary-output=e:\b\swarm_slave\w\iomwmbws\output.json

[panicker, 2017-04-19 23:00:32]

On 2017/04/19 21:47:39, Roger McFarlane (Chromium) wrote:
> On 2017/04/19 21:26:42, panicker wrote:
> > LGTM.
> > For the roll forward, could you indicate how to run the failing test? 
> > Is it flaky or failing consistently? Did it run on Presubmit?
> > Thanks!
> 
> this should do the trick...
> 
> cc_unittests
>
--gtest_filter=LayerTreeHostProxyTestActivationTime.RunMultiThread_DelegatingRenderer
> 
> That runs only the test that failed.
> 
> The command on the bot that ran the entire suite was:
> 
> cc_unittests.exe --brave-new-test-launcher --test-launcher-bot-mode
> --test-launcher-summary-output=e:\b\swarm_slave\w\iomwmbws\output.json

That's the test I added and it passes for me locally and on other platforms (in
trybot).
so question is whether it fails consistently on windows or is flaky.

[panicker, 2017-04-19 23:22:12]

On 2017/04/19 23:00:32, panicker wrote:
> On 2017/04/19 21:47:39, Roger McFarlane (Chromium) wrote:
> > On 2017/04/19 21:26:42, panicker wrote:
> > > LGTM.
> > > For the roll forward, could you indicate how to run the failing test? 
> > > Is it flaky or failing consistently? Did it run on Presubmit?
> > > Thanks!
> > 
> > this should do the trick...
> > 
> > cc_unittests
> >
>
--gtest_filter=LayerTreeHostProxyTestActivationTime.RunMultiThread_DelegatingRenderer
> > 
> > That runs only the test that failed.
> > 
> > The command on the bot that ran the entire suite was:
> > 
> > cc_unittests.exe --brave-new-test-launcher --test-launcher-bot-mode
> > --test-launcher-summary-output=e:\b\swarm_slave\w\iomwmbws\output.json
> 
> That's the test I added and it passes for me locally and on other platforms
(in
> trybot).
> so question is whether it fails consistently on windows or is flaky.

Looks like it fails consistently on win7 (and win_chromium_dbg_ng is not
included in the presubmit run)