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

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


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

chromium-rel-mac-hdd

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

===== 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@405320  19.9775  2.27477  8   good
chromium@405396  21.6646  4.24804  11  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 629302

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___www.amazon.com
Relative Change: 2.21%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/650
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006759115318690784


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

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

Passing the last few on to the current perf sheriff for triage...

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

Trying a couple of new bisects.

===== 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@405300  21.2092  4.13619  12  good
chromium@405410  20.5488  1.73432  12  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 629302

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___www.amazon.com
Relative Change: 6.88%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/689
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005516748480645584


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

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

Perf sheriff ping: reminder to follow up on possible performance issues

Perf sheriff ping

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/848
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Current numbers are far below original alert level.

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