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

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


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

android-nexus6
chromium-rel-mac-retina
chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-gpu-ati
linux-release

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

=== 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_nexus6_perf_bisect
  Benchmark    : speedometer2
  Metric       : Vanilla-ES2015-TodoMVC/Speedometer2


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=Speedometer2 speedometer2

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

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


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14fb4604040000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14b72ad8040000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14b72ad8040000