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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_JK88AgM


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

chromium-rel-win7-x64-dual

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

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

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


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : ulan
  Commit : 95e17ac4602dc38aaa6a44d4f6d2566920d6c75d
  Date   : Fri Apr 07 09:00:03 2017
  Subject: Ensure fixed amount of scrolling in infinite scroll stories.

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.infinite_scroll-classic_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max
  Change       : 21.86% | 60536968.5333 -> 73770598.4

Revision             Result                   N
chromium@462557      60536969 +- 3210310      6      good
chromium@462704      59488393 +- 2172687      6      good
chromium@462777      60488636 +- 6154376      6      good
chromium@462796      59055582 +- 2496477      6      good
chromium@462805      61414878 +- 6336153      6      good
chromium@462810      58662366 +- 2063347      6      good
chromium@462812      58933248 +- 1258291      6      good
chromium@462813      72389973 +- 3576449      6      bad       <--
chromium@462814      72424926 +- 3676501      6      bad
chromium@462850      73770598 +- 2584479      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 v8.infinite_scroll-classic_tbmv2

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982713932370383792

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4887174425608192


| 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 Speed>Bisection.  Thank you!

 Issue 713121  has been merged into this issue.

 Issue 712465  has been merged into this issue.

 Issue 717759  has been merged into this issue.

This change is causing failures as well as regressions. 

The android failures will be fixed by https://codereview.chromium.org/2857923003/

There are no other failures, right?

Yep, those are the ones I was talking about. Thanks!

The regressions are due to benchmark change.