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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : story:power_avg/browse_social/browse_social_facebook_infinite_scroll

Revision             Result                   N
chromium@487870      1.9456 +- 0.497671       14      good
chromium@487946      1.90494 +- 0.683797      19      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.facebook.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/8973437419689288496


For feedback, file a bug with component Speed>Bisection

Must not be the real thing.