Revert adding telemetry perf unit tests to Android trybots.

Revert adding telemetry perf unit tests to Android trybots.

This has regressed from 2.5 minutes when it was added 3 weeks ago to 7 minutes now. See http://build.chromium.org/p/tryserver.chromium.linux/stats/linux_android_rel_ng

BUG=379378
R=zhenw@chromium.org

Committed: https://chromium.googlesource.com/chromium/src/+/2bd661311e3192357d72532c87b575bb0f37ae7b

[jam, 2015-05-27 17:11:14]

jam@chromium.org changed reviewers:
+ zhenw@chromium.org

[Zhen Wang, 2015-05-27 17:39:54]

zhenw@chromium.org changed reviewers:
+ nednguyen@google.com

[Zhen Wang, 2015-05-27 17:39:54]

+nednguyen

The telemetry_perf_unittests now take around 7 minutes on CQ and every test
passes without retry. I can see two related reasons.
1. The number of tests increase from 100 to 120.
2. The number of Android devices decrease from 8 to 6/7 on CQ.

nednguyen@, shall we limit the number of tests we want to run on CQ?

jam@, is there any reason why the number of Android devices is reduced?

I will investigate more locally.

[jam, 2015-05-27 17:41:31]

On 2015/05/27 17:39:54, Zhen Wang wrote:
> +nednguyen
> 
> The telemetry_perf_unittests now take around 7 minutes on CQ and every test
> passes without retry. I can see two related reasons.
> 1. The number of tests increase from 100 to 120.
> 2. The number of Android devices decrease from 8 to 6/7 on CQ.
> 
> nednguyen@, shall we limit the number of tests we want to run on CQ?

I was under the impression that this would stay at 2.5 minutes.

I would prefer we revert this now, and then others can investigate
asynchronously (i.e. like with any regression).

> 
> jam@, is there any reason why the number of Android devices is reduced?

This happened with the switch to N5 from N4. However the other test suites
didn't regress (since the devices are faster).

Either way, this is orthogonal because this isn't what caused 2.5minutes-> 7
minutes jump.

> 
> I will investigate more locally.

[Zhen Wang, 2015-05-27 17:42:41]

On 2015/05/27 17:41:31, jam wrote:
> On 2015/05/27 17:39:54, Zhen Wang wrote:
> > +nednguyen
> > 
> > The telemetry_perf_unittests now take around 7 minutes on CQ and every test
> > passes without retry. I can see two related reasons.
> > 1. The number of tests increase from 100 to 120.
> > 2. The number of Android devices decrease from 8 to 6/7 on CQ.
> > 
> > nednguyen@, shall we limit the number of tests we want to run on CQ?
> 
> I was under the impression that this would stay at 2.5 minutes.
> 
> I would prefer we revert this now, and then others can investigate
> asynchronously (i.e. like with any regression).
> 
> > 
> > jam@, is there any reason why the number of Android devices is reduced?
> 
> This happened with the switch to N5 from N4. However the other test suites
> didn't regress (since the devices are faster).
> 
> Either way, this is orthogonal because this isn't what caused 2.5minutes-> 7
> minutes jump.
> 
> > 
> > I will investigate more locally.

lgtm

[jam, 2015-05-27 17:46:11]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2015-05-27 17:48:26]

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

[Zhen Wang, 2015-05-27 21:34:35]

It seems that linux_android_rel_ng is getting many failures.

[commit-bot: I haz the power, 2015-05-28 00:21:01]

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

[jam, 2015-05-28 00:21:17]

Committed patchset #1 (id:1) manually as
2bd661311e3192357d72532c87b575bb0f37ae7b.