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

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


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

chromium-rel-win7-dual
chromium-rel-win7-x64-dual

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/https___www.google.com_search?q_cats_tbm_isch


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https...www.google.com.search.q.cats.tbm.isch smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

Looks like this got interrupted, re-kicking.

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/Blogger

Revision             Result                  N
chromium@489889      18.5502 +- 3.0651       21      good
chromium@489968      18.4732 +- 2.90598      21      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=Blogger smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : smoothness.top_25_smooth
  Metric       : frame_times/https___www.google.com_search?q_cats_tbm_isch


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https...www.google.com.search.q.cats.tbm.isch smoothness.top_25_smooth

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

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


For feedback, file a bug with component Speed>Bisection

The test is failing, but one of the bisect got before/after results and there wasn't a regression reproduced.