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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyJHOvgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyKXgowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyMWiuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyO-_uwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqKj0ogsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyNuQswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqIzfswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyOGGowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyL3GswoM


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

android-galaxy-s5
android-nexus5
android-nexus6
android-nexus9
chromium-rel-mac-retina
chromium-rel-mac10

===== 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 Value  Std. Dev.   Num Values  Good?
chromium@384927         160.926346  21.9353     18          good
chromium@384932         162.350177  41.925698   18          bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 600653

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: input_event_latency_discrepancy/input_event_latency_discrepancy
Relative Change: 5.15%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2076
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9016239150702151152


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

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

Kicked off another bisect on a larger regression: https://chromeperf.appspot.com/buildbucket_job_status/9016216304853603968

For the mac cases; see graph: https://chromeperf.appspot.com/report?sid=5e775f30af908f72149a5b5ab231da0ff129f1f65b4c2f9c71b3cd6d2eeff25f&start_rev=382063&end_rev=385151

There was a data stoppage (which was seen as an improvement; change https://chromium.googlesource.com/chromium/src/+/ca4feba9a31e10d1baab5813650c192e06cfd643) and a subsequent fix ensure all the tests are reporting in https://chromium.googlesource.com/chromium/src/+/581656043e63a1e26fb6b038823b2d0bb2a28710

As for the other tests I'm not sure they involve input something else might be going on with those tests.

sullivan@; please see comment #4.

dtapushka: Thanks! I split off the other regressions (which appear to be a revert of an improvement in memory on android) into  bug 600708 . Can this one be closed per comment 4?

Closing as per this is expected. 

There was a data stoppage and the stoppage was resolved. See  issue 596823  detailing the data stoppage.

=== 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 : Fix Event Latency Info on generate gesture events.
Author  : dtapuska
Commit description:
  
Generated gesture events weren't marking the begin component
correctly which caused the tag not to be set correctly.
In order to achieve this proper marking the events need
to propagate up from the InputRouterImpl into the
RenderWidgetHostImpl which adds the latency information.

BUG= 596823 

Review URL: https://codereview.chromium.org/1847823005

Cr-Commit-Position: refs/heads/master@{#384951}
Commit  : 581656043e63a1e26fb6b038823b2d0bb2a28710
Date    : Mon Apr 04 18:01:27 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@384927         290.76092   68.021694   5           good
chromium@384939         377.45084   40.89145    5           good
chromium@384947         364.286     95.464683   5           good
chromium@384949         280.5826    102.500036  5           good
chromium@384950         399.84072   15.570814   5           good
chromium@384951         1740.85338  297.298174  5           bad         <-
chromium@384954         2149.9889   243.728848  5           bad
chromium@384974         1562.18042  131.723278  5           bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 600653

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests smoothness.gpu_rasterization.top_25_smooth
Test Metric: input_event_latency_discrepancy/https___plus.google.com_110031535020051778989_posts
Relative Change: 437.27%
Score: 99.9

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


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

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