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

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


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

win-zenbook

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/488
Failure reason: the build has failed due to infrastructure failure.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/517
Failure reason: the build has failed due to infrastructure failure.

perf sheriff fixit: unassigning bugs owned by perf sheriffs to clarify that the rotation is responsible for triage.

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

=== PERF REGRESSION ===


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

Hi jbauman@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 : Enable GPU rasterization on Windows Intel Broadwell and later GPUs.
Author  : jbauman
Commit description:
  
List from
https://cgit.freedesktop.org/vaapi/intel-driver/tree/src/i965_pciids.h

BUG= 646135 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2337863002
Cr-Commit-Position: refs/heads/master@{#419047}
Commit  : 0ad321336ed38d8a281d2da084013cf1e29b2ce0
Date    : Fri Sep 16 00:16:38 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@419044  587.663  21.1428  8  good
chromium@419046  587.826  22.8219  8  good
chromium@419047  807.084  51.288   5  bad    <--
chromium@419048  808.121  32.1167  5  bad
chromium@419052  807.153  64.3724  5  bad
chromium@419059  809.578  61.9647  5  bad
chromium@419073  796.647  62.8527  5  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 648649

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.html5rocks.com.en. page_cycler_v2.typical_25
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.html5rocks.com_en_
Relative Change: 35.56%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/619
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994346859354148688


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

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

This test seems to not have run on this bot since October 8th or so.

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

Test seems to have disappeared.