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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp5eXtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp7WmtQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp4e-4QgM


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

This is a recovery to past levels after a recent improvement.

=== PERF REGRESSION ===


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

Hi sunyunjia@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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


===== SUSPECTED CL(s) =====
Subject : Reset the default value of touch event flag back to "Auto".
Author  : sunyunjia
Commit description:
  
This is a partial revert of issue 2467913002.
https://codereview.chromium.org/2467913002

In the previous patch, we set the default value of touch-event-api as enabled.
However, this may cause troubles due to  http://crbug.com/392584 . Basically
there are still a bunch of websites on which mouse support is broken when the
TouchEvents API is present. So we need to retain the "auto" behavior as the
default. We also keep firing DOM events as before even when the flag says
disabled.

BUG= 644318 ,  669386 , 669132

Review-Url: https://codereview.chromium.org/2531413002
Cr-Commit-Position: refs/heads/master@{#435821}
Commit  : 78171bf829d1ae47b7d7237c08878783a2cdadb5
Date    : Fri Dec 02 02:07:52 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@435722  21.8106  12.125   25  good
chromium@435782  20.0032  2.4764   25  good
chromium@435812  20.2188  2.84016  25  good
chromium@435820  19.9054  2.038    25  good
chromium@435821  25.0254  3.04902  25  bad    <--
chromium@435822  24.9446  3.80776  25  bad
chromium@435824  24.8718  3.05876  25  bad
chromium@435827  23.7282  9.98373  25  bad
chromium@435842  25.0666  2.71874  25  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 671026

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.paint
Test Metric: color-changes/color-changes
Relative Change: 14.93%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1966
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994183234248472544


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

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