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

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


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

android-nexus5X
android-nexus7v2

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

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

Error: BUILD_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: c9e738432a1bce852e99ba4deb9f9dcac8450fdd
  bad_revision : 7ac4e75787ae3b44a33026e4e3671410c81a273c

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : cpu_time_percentage_avg/browse_social/browse_social_pinterest_infinite_scroll

Revision             Result                      N
chromium@503949      0.711925 +- 0.0095083       6      good
chromium@503951      0.775326 +- 0.00833835      6      bad
chromium@503953      0.778435 +- 0.0096871       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 --story-filter=browse.social.pinterest.infinite.scroll system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

This graph recovers. WontFix.