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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrP7npAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrKW6tgoM


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

android-nexus5X
android-nexus6

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_main_thread_scroll_latency/mean_main_thread_scroll_latency


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 scheduler.tough_scheduling_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983986901127863600

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5522114976677888


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

a device seems to be offline. filed a bug 705439

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

was a temporary spike (noise)