Revert of re-enable PCv2 on non-ref Android

Revert of re-enable PCv2 on non-ref Android (patchset #1 id:1 of https://codereview.chromium.org/2030523003/ )

Reason for revert:
page_cycler_v2.typical_25 fails on Android perf bot. See http://crbug.com/616781

Original issue's description:
> re-enable PCv2 on non-ref Android
> 
> BUG=615178
> 
> Committed: https://crrev.com/b34eeae48ba79e80c4ec601922459d77af905f5a
> Cr-Commit-Position: refs/heads/master@{#397120}

TBR=nednguyen@google.com,kouhei@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615178

[Zhen Wang, 2016-06-03 01:42:08]

The CQ bit was checked by zhenw@chromium.org

[Zhen Wang, 2016-06-03 01:42:08]

Created Revert of re-enable PCv2 on non-ref Android

[commit-bot: I haz the power, 2016-06-03 01:43:16]

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

[nednguyen, 2016-06-03 01:48:54]

The CQ bit was unchecked by nednguyen@google.com

[nednguyen, 2016-06-03 01:49:38]

On 2016/06/03 01:43:16, commit-bot: I haz the power wrote:
> CQ is trying da patch. Follow status at
>  https://chromium-cq-status.appspot.com/patch-status/2030713005/1
> View timeline at
>  https://chromium-cq-status.appspot.com/patch-timeline/2030713005/1

Zhen: can we disable this only the Android perf bots?

[Zhen Wang, 2016-06-03 01:51:00]

On 2016/06/03 01:49:38, nednguyen wrote:
> On 2016/06/03 01:43:16, commit-bot: I haz the power wrote:
> > CQ is trying da patch. Follow status at
> >  https://chromium-cq-status.appspot.com/patch-status/2030713005/1
> > View timeline at
> >  https://chromium-cq-status.appspot.com/patch-timeline/2030713005/1
> 
> Zhen: can we disable this only the Android perf bots?

Do you mean keep the reference?

[Zhen Wang, 2016-06-03 01:53:23]

On 2016/06/03 01:51:00, Zhen Wang wrote:
> On 2016/06/03 01:49:38, nednguyen wrote:
> > On 2016/06/03 01:43:16, commit-bot: I haz the power wrote:
> > > CQ is trying da patch. Follow status at
> > >  https://chromium-cq-status.appspot.com/patch-status/2030713005/1
> > > View timeline at
> > >  https://chromium-cq-status.appspot.com/patch-timeline/2030713005/1
> > 
> > Zhen: can we disable this only the Android perf bots?
> 
> Do you mean keep the reference?

Wait. This CL was just about enabling on Android Perf reference builds. What do
you mean exactly?

[nednguyen, 2016-06-03 01:54:52]

On 2016/06/03 01:51:00, Zhen Wang wrote:
> On 2016/06/03 01:49:38, nednguyen wrote:
> > On 2016/06/03 01:43:16, commit-bot: I haz the power wrote:
> > > CQ is trying da patch. Follow status at
> > >  https://chromium-cq-status.appspot.com/patch-status/2030713005/1
> > > View timeline at
> > >  https://chromium-cq-status.appspot.com/patch-timeline/2030713005/1
> > 
> > Zhen: can we disable this only the Android perf bots?
> 
> Do you mean keep the reference?

I mean the flaky failures are not on all android bots, just "Android Nexus5X
WebView Perf" & "Android One Perf (1)". Can we only disable the benchmarks on
those bots?

[Zhen Wang, 2016-06-03 01:59:23]

> I mean the flaky failures are not on all android bots, just "Android Nexus5X
> WebView Perf" & "Android One Perf (1)". Can we only disable the benchmarks on
> those bots?

I see. How to detect "Android Nexus5X WebView Perf"?

And does reference make a difference here? I see in the bug that the failure
test does not have "reference" label, but bisect points to this CL.

[nednguyen, 2016-06-03 02:36:39]

On 2016/06/03 01:59:23, Zhen Wang wrote:
> > I mean the flaky failures are not on all android bots, just "Android Nexus5X
> > WebView Perf" & "Android One Perf (1)". Can we only disable the benchmarks
on
> > those bots?
> 
> I see. How to detect "Android Nexus5X WebView Perf"?
> 
> And does reference make a difference here? I see in the bug that the failure
> test does not have "reference" label, but bisect points to this CL.

For 5x:
https://code.google.com/p/chromium/codesearch#chromium/src/tools/perf/benchma...

[nednguyen, 2016-06-03 02:37:45]

>> I see in the bug that the failure
> > test does not have "reference" label, but bisect points to this CL.

This is because the original CL was about reenable the actual benchmark on
Android & disable the reference benchmark on Android.

[Zhen Wang, 2016-06-03 06:41:33]

Based on the discussion with Ned, we decided to disable the test on Android One
and Nexus 5X only, and not revert the original CL.

Closing this CL without commit now. See
https://codereview.chromium.org/2030243003/

[Zhen Wang, 2016-06-03 06:41:46]

Description was changed from

==========
Revert of re-enable PCv2 on non-ref Android (patchset #1 id:1 of
https://codereview.chromium.org/2030523003/ )

Reason for revert:
page_cycler_v2.typical_25 fails on Android perf bot. See http://crbug.com/616781

Original issue's description:
> re-enable PCv2 on non-ref Android
> 
> BUG=615178
> 
> Committed: https://crrev.com/b34eeae48ba79e80c4ec601922459d77af905f5a
> Cr-Commit-Position: refs/heads/master@{#397120}

TBR=nednguyen@google.com,kouhei@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615178
==========

to

==========
Revert of re-enable PCv2 on non-ref Android (patchset #1 id:1 of
https://codereview.chromium.org/2030523003/ )

Reason for revert:
page_cycler_v2.typical_25 fails on Android perf bot. See http://crbug.com/616781

Original issue's description:
> re-enable PCv2 on non-ref Android
> 
> BUG=615178
> 
> Committed: https://crrev.com/b34eeae48ba79e80c4ec601922459d77af905f5a
> Cr-Commit-Position: refs/heads/master@{#397120}

TBR=nednguyen@google.com,kouhei@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615178
==========