All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=765122

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3f8ce09706d23075aca2c7d006ac172c3c243dc372a830879d772ddcb9f609d3


Bot(s) for this bug's original alert(s):

android-nexus6

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 13ce8f521d57f624eed2588e6bc30713e376a55d
  bad_revision : b3798f15aba08f6c3af039116c200002ba35c659

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : typed-array-set-from-typed/typed-array-set-from-typed

Revision             Result                   N
chromium@501007      193.16 +- 2.28683        6      good
chromium@501090      192.839 +- 2.60973       6      good
chromium@501131      192.539 +- 0.751816      5      good
chromium@501152      192.367 +- 2.02141       6      good
chromium@501172      157.244 +- 1.83952       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings

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

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


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : typed-array-set-from-typed/typed-array-set-from-typed


Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings

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

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


For feedback, file a bug with component Speed>Bisection

Looks like bisect couldn't track it down.