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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_browser_cpu_time_per_frame/infinite_scrolling.html
  Change       : 0.93% | 4.01878293793 -> 4.03496018435

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/587f2238d3e7e98255914371e8f2dc8a08c7e378..126a0e6e97f36b67ddcc38569e946c5621aeb643


Revision             Result                    N
chromium@517669      4.01878 +- 0.079745       14       good
chromium@517687      4.01765 +- 0.051913       14       good
chromium@517690      4.01644 +- 0.0930642      21       good
chromium@517691      ---                       ---      build failure
chromium@517692      ---                       ---      build failure
chromium@517693      ---                       ---      build failure
chromium@517694      4.03744 +- 0.0677105      14       bad
chromium@517700      4.03496 +- 0.0615715      14       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 --story-filter=infinite.scrolling.html thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_browser_cpu_time_per_frame/infinite_scrolling.html
  Change       : 1.09% | 4.00219433074 -> 4.03620219328

Suspected Commit Range
  7 commits in range
  https://chromium.googlesource.com/chromium/src/+log/7b33c549911215282621c311701672fa3fd672cf..20a2f79a07d5664411e1f65b7ba4ca8ac4197d2f


Revision             Result                    N
chromium@517669      4.00219 +- 0.0333723      9        good
chromium@517685      4.01749 +- 0.0749729      14       good
chromium@517693      4.01754 +- 0.0860526      14       good
chromium@517694      ---                       ---      build failure
chromium@517695      ---                       ---      build failure
chromium@517696      ---                       ---      build failure
chromium@517697      ---                       ---      build failure
chromium@517698      ---                       ---      build failure
chromium@517699      ---                       ---      build failure
chromium@517700      4.0362 +- 0.0634478       14       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 --story-filter=infinite.scrolling.html thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection

Bisect isn't actually reproing.