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

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


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

chromium-rel-win10
chromium-rel-win8-dual

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

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

Hi chrishtr@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 : SPv2: Add support for tracking raster paint invalidations in testing.
Author  : chrishtr
Commit description:
  
Adds one test to demonstrate the output format and smoke test SPv2 paint invalidation.

BUG= 647831 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

Review-Url: https://codereview.chromium.org/2380683006
Cr-Commit-Position: refs/heads/master@{#422459}
Commit  : a3396125b597b2c83bd7617405c44ecf8c958985
Date    : Mon Oct 03 18:06:48 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@422450  16.3334  0.225912  8  good
chromium@422456  16.3562  0.255178  5  good
chromium@422458  16.3001  0.201738  5  good
chromium@422459  16.8239  0.123161  5  bad    <--
chromium@422461  16.7544  0.209716  8  bad
chromium@422471  16.939   0.220004  8  bad
chromium@422491  16.7349  0.222132  8  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 653561

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.key_desktop_move_cases
Test Metric: mean_input_event_latency/mean_input_event_latency
Relative Change: 2.95%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2226
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999539672518658560


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

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

From the graphs, it looks like the graphics are about back to where they
were before commit 421534. I went through my patch twice in the past few
days looking for accidental extra code paths that are not only for testing
(the patch refactors testing-only flows) and found none.

As a result, closing.

I agree with this assessment. Thanks for the due diligence.