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

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


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

chromium-rel-mac11

===== 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@391500  27.2518  2.47886  12  good
chromium@391650  28.2811  3.16231  12  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 610240

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/https___mail.google.com_mail_
Relative Change: 4.94%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/629
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151642407834240


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

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

===== 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@391580  30.8386  2.50511  12  good
chromium@391618  30.6951  1.65487  12  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 610240

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/https___mail.google.com_mail_
Relative Change: 2.27%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/628
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013151662927402784


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

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

Trying a wider bisect.

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


===== SUSPECTED CL(s) =====
Subject : This change enables GPU Raster on OSX.
Author  : ericrk
Commit description:
  
I've compiled a bit of benchmark data to support turning this on -
https://docs.google.com/a/google.com/document/d/1RPEnillJOaOKW47t9DYuttQkvWDo7ilx9KDB_nJnwpc/edit?usp=sharing
Still filling in more data, but I'm pretty happy with the results so far. In
a number of cases we have a performance win, and in most cases we have a power win.

Checking this in now will give us a long canary period before the next branch
point to catch any issues.

BUG= 542959 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_optional_gpu_tests_rel;tryserver.chromium.mac:mac_optional_gpu_tests_rel;tryserver.chromium.win:win_optional_gpu_tests_rel;tryserver.blink:mac_blink_rel

Review-Url: https://codereview.chromium.org/1881053003
Cr-Commit-Position: refs/heads/master@{#391655}
Commit  : 8325892c2efdef8cff86ba16e7569f8b424daeda
Date    : Wed May 04 22:14:40 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@391300  29.9158  2.8378    5  good
chromium@391550  30.862   2.5415    5  good
chromium@391613  33.0008  1.01637   5  good
chromium@391644  30.64    2.28888   5  good
chromium@391652  30.5748  0.857441  5  good
chromium@391654  30.3364  0.773161  5  good
chromium@391655  40.7332  1.66999   5  bad    <--
chromium@391656  40.4822  0.789832  5  bad
chromium@391660  41.1946  1.58041   5  bad
chromium@391675  39.9524  1.48502   5  bad
chromium@391800  41.0414  1.09648   5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 610240

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/https___mail.google.com_mail_
Relative Change: 37.19%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/630
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9013132439627318800


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

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