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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggv-crwsM


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

chromium-rel-mac-retina

=== Auto-CCing suspected CL author wangxianzhu@chromium.org ===

Hi wangxianzhu@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Check DisplayItemCient aliveness in cached subsequences
Author  : wangxianzhu
Commit description:
  
BUG=609218

Review-Url: https://codereview.chromium.org/2066603005
Cr-Commit-Position: refs/heads/master@{#400607}
Commit  : 127e5fadca5f431a5de1bef939f7f43aec1d136f
Date    : Sun Jun 19 03:13:42 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev    N  Good?
chromium@400605  15.9804  0.0984241  5  good
chromium@400606  16.0088  0.10554    5  good
chromium@400607  16.5758  0.19673    5  bad    <--
chromium@400609  16.3734  0.147309   5  bad
chromium@400612  16.4462  0.123839   5  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 621585

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/http___games.yahoo.com
Relative Change: 2.91%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1347
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009315762086344464


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5901920993017856

| 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!

This is temporary for diagnosing bug 609218.

Thanks for the update. It should be fine as long as these regressions don't make it m-53 stable which seems to be the plan.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@400609  16.3925  0.15463   18  good
chromium@400612  16.4007  0.208981  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 621585

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: mean_input_event_latency/http___games.yahoo.com
Relative Change: 0.15%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1346
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9009315805173279984


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5826898920210432

| 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!

Restored.