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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=e79622f4f33af1303c7b1563115464e83762307dcf3ddb637e96bdd43f3399a4


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

chromium-rel-win10
chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 74cabe344138045a60157eecf6f6514de0230c0c
  bad_revision : 90ac48ae82f230d3287d8bbd3b808490f9aa48cd

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_filters_cases
  Metric       : frame_times/IE PirateMark

Revision             Result                   N
chromium@493198      18.0623 +- 0.511126      6      good
chromium@493236      18.0047 +- 0.497795      6      good
chromium@493248      17.7896 +- 0.349491      6      good
chromium@493260      20.1879 +- 0.849228      6      bad
chromium@493275      20.4085 +- 0.581697      6      bad
chromium@493351      20.4262 +- 0.578392      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=IE.PirateMark smoothness.gpu_rasterization.tough_filters_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8971523564860610816


For feedback, file a bug with component Speed>Bisection

Re-kicking failed bisect.

Actually, scratch that, this recovered.