Will kick a return code bisect.

This is because of 

Disable retries for angle_perftests
https://chromium-review.googlesource.com/784124

eakuefner if you want to disable the tests on this configuration feel free.

Yuly can you investigate on a local device?

The test timeout seems to be in "Uniforms_gles_400_vec4_repeating" but it could be some resource leak either in ANGLE or in the driver. Not sure.

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8961109674622823696

Last passing build that had a timeout:

https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5X%20Perf/863
https://chromium-swarm.appspot.com/task?id=3a2129f7f57d7010&refresh=10&show_raw=1

=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : angle_perftests
  Metric       : BufferSubData_gles_float4_every1/score

Revision             Exit Code      N
chromium@520107      1 +- N/A       2      good
chromium@520294      1 +- N/A       2      bad

To Run This Test
  ./src/out/Release/angle_perftests --test-launcher-print-test-stdio=always --test-launcher-jobs=1

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8961109674622823696


For feedback, file a bug with component Speed>Bisection

I think the problem is that gtest shard times out after default 120 seconds.
I'll increase that to 180.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/64f92f18cc2ebc737378455b6ec8aa0fa0d5c4bf

commit 64f92f18cc2ebc737378455b6ec8aa0fa0d5c4bf
Author: Yuly Novikov <ynovikov@chromium.org>
Date: Tue Dec 05 00:52:52 2017

Increase angle_perftests shard timeout

BUG= 791656 
TBR=eyaich@chromium.org

Change-Id: I5cb3a2438db14009a308e3489d7719a53bf4134d
Reviewed-on: https://chromium-review.googlesource.com/806445
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521558}
[modify] https://crrev.com/64f92f18cc2ebc737378455b6ec8aa0fa0d5c4bf/testing/buildbot/chromium.perf.json
[modify] https://crrev.com/64f92f18cc2ebc737378455b6ec8aa0fa0d5c4bf/tools/perf/core/perf_data_generator.py

Seems to have cleared up. Thanks for the fix Yuly.

 Issue 791655  has been merged into this issue.