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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : thread_total_all_cpu_time_per_second/set-timeout.html (Long Idle)

Revision             Result                    N
chromium@525031      0.213699 +- 0.133838      21      good
chromium@525137      0.212304 +- 0.13392       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=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Kicking off a few more bisects.

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

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

This only happened on one device, and bisect can't reproduce.