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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg56PjtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp7WxrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg59WatQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg54rgpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp-GeswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg57GmuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp7-19wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-6y6wwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp6uR8woM


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

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

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

===== 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@435724  1564.35  509.169  8   good
chromium@435782  2162.48  6846.99  12  good
chromium@435812  1724.25  2740.07  12  good
chromium@435820  1577.06  885.878  12  good
chromium@435821  2213.06  1656.32  8   bad    <--
chromium@435822  2762.48  8139.71  12  bad
chromium@435824  2549.23  3542.87  8   bad
chromium@435827  2018.27  659.442  8   bad
chromium@435842  2486.16  3588.74  8   bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 671059

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.theverge.com.2013.3.5.4061684.inside.ted.the.smartest.bubble.in.the.world page_cycler_v2.typical_25
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.theverge.com_2013_3_5_4061684_inside-ted-the-smartest-bubble-in-the-world
Relative Change: 58.93%

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


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

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