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

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


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

android-nexus6

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

=== 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    : thread_times.key_silk_cases
  Metric       : thread_browser_cpu_time_per_frame/inbox_app.html?toggle_drawer

Revision             Result                    N
chromium@522049      1.85768 +- 0.0951815      21      good
chromium@522066      1.85173 +- 0.10123        21      unknown
chromium@522083      1.83979 +- 0.0724459      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=inbox.app.html.toggle.drawer thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection

The bisect numbers look like it actually saw a slight improvement; the graph is noisy and this doesn't repro.