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

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

The bisect was able to narrow the range, you can try running with:
  good_revision: 06ef13df196b1a7f427c5d440e982d48c34623e4
  bad_revision : fd98b65e68c329ff0bb43db5a1c15e50aaa6c66d

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


Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_facebook_infinite_scroll
  Change       : 205.59% | 1.58583333333 -> 4.84616666667

Revision             Result                   N
chromium@478963      1.58583 +- 0.29703       6      good
chromium@479009      1.54033 +- 0.357241      6      good
chromium@479021      1.58217 +- 0.321834      6      good
chromium@479027      1.58583 +- 0.435278      6      good
chromium@479030      5.65833 +- 1.05101       6      bad
chromium@479032      5.3085 +- 0.76426        6      bad
chromium@479055      4.84617 +- 3.42345       6      bad

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=browse.social.facebook.infinite.scroll v8.browsing_desktop

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

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


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

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

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

The bisect was able to narrow the range, you can try running with:
  good_revision: 06ef13df196b1a7f427c5d440e982d48c34623e4
  bad_revision : fd98b65e68c329ff0bb43db5a1c15e50aaa6c66d

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


Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_facebook_infinite_scroll
  Change       : 214.73% | 1.66733333333 -> 5.24766666667

Revision             Result                   N
chromium@478963      1.66733 +- 0.443438      6      good
chromium@479009      1.5375 +- 0.177103       6      good
chromium@479021      1.583 +- 0.325951        6      good
chromium@479027      1.58133 +- 0.200168      6      good
chromium@479030      4.27856 +- 5.36258       9      bad
chromium@479032      5.40817 +- 0.538255      6      bad
chromium@479055      5.24767 +- 0.564184      6      bad

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=browse.social.facebook.infinite.scroll v8.browsing_desktop

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

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


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

Believe this is a dupe, since it actually finds the same commit but for whatever reason   the bisect thinks it's not yet done.