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

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


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

android-nexus7v2
chromium-rel-mac-retina

Sent off some more bisects.

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

Hi dtapuska@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 : Remove the default wheel event handler from blink.
Author  : dtapuska
Commit description:
  
Wheel gesture scrolls are used solely now. Remove the
defaultWheelEventHandler code as it is unused.

Also remove the WebSetting for wheel gesture support.

BUG= 598798 

Review-Url: https://codereview.chromium.org/2049493002
Cr-Commit-Position: refs/heads/master@{#398618}
Commit  : 256b95a4dce8f1e57e69ff0032ee16d4c76e580b
Date    : Wed Jun 08 18:12:34 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@398614  591.995  6.77538  12  good
chromium@398617  591.877  4.27613  8   good
chromium@398618  603.644  4.4495   5   bad    <--
chromium@398619  599.222  4.99218  12  bad
chromium@398624  600.332  6.9024   12  bad
chromium@398634  597.894  6.8506   18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 618620

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: AngularJS-TodoMVC/AngularJS-TodoMVC
Relative Change: 1.15%
Score: 99.5

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


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

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

I don't think my change removing some unused support for scrolling should have changed a js benchmark.

I'm re-running the bisect for the android bot with a larger range. But the mac metric didn't move all so much and that was what was used to assign this bug to me. 

Assigning to test metric owner. The bisect bot finds nothing useful.

Likewise the metric at ToT is better than it was ever before. So I'm not sure if this is still an issue or this can just be closed since there isn't a regression against ToT.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This has recovered.