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

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


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

android-one

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

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : loading.mobile
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                   N
chromium@483330      67.9096 +- 0.517934      6      good
chromium@483426      68.4792 +- 0.534922      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 loading.mobile

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

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


For feedback, file a bug with component Speed>Bisection