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

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


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

android-one

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ericrk
  Commit : 2d930bf540c443c992843ab4199af12b2e14848f
  Date   : Mon Jan 30 16:58:39 2017
  Subject: Revert of Temporarily disable context idle cleanup. (patchset #2 id:20001 of https://codereview.chromium.org/2651703004/ )

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.polymer
  Metric       : mean_input_event_latency/mean_input_event_latency
  Change       : 34.67% | 82.0354583333 -> 110.473395833

Revision             Result                  N
chromium@446977      82.0355 +- 4.60807      6      good
chromium@446992      81.6699 +- 2.76274      6      good
chromium@446999      84.2585 +- 2.48389      6      good
chromium@447003      83.029 +- 6.50448       6      good
chromium@447004      114.09 +- 5.93545       6      bad       <--
chromium@447005      113.353 +- 5.22115      6      bad
chromium@447006      110.473 +- 6.06611      6      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 smoothness.gpu_rasterization.polymer

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

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


| 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 Tests>AutoBisect.  Thank you!