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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_renderer_compositor_cpu_time_per_frame/http___cuteoverload.com

Revision             Result                   N
chromium@490131      2.67636 +- 0.425912      21       good
chromium@490190      2.65976 +- 0.337566      14       good
chromium@490219      2.65847 +- 0.555533      21       good
chromium@490220      ---                      ---      build failure
---                  ---                      ---      too many build failures to list
chromium@490225      2.68825 +- 0.509341      21       unknown
chromium@490243      ---                      ---      build failure
chromium@490244      2.76391 +- 0.510602      21       bad
chromium@490250      2.7589 +- 0.524646       14       bad
chromium@490368      2.78415 +- 0.422284      21       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=http...cuteoverload.com thread_times.key_mobile_sites_smooth

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

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


For feedback, file a bug with component Speed>Bisection

This looks like noise.