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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg3-3VuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg397ZrgkM


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/8991947693857530400

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision  Mean  Std Dev  N  Good?

Bisect job ran on: win_perf_bisect
Bug ID: 677454

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests startup.warm.blank_page
Test Metric: open_tabs_time/open_tabs_time
Relative Change: 0.00%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/7086
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8991947693857530400


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

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

Filed crbug.com/677843 to investigate the lack of values.

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time

Revision      Result      N

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 startup.warm.blank_page

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time

Revision      Result      N

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests startup.warm.blank_page

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

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


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

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time


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 startup.warm.blank_page

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

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


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

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time


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 startup.warm.blank_page

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

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


| 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/8982624187905102176

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.