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

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


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

chromium-rel-win7-gpu-nvidia

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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@434982  5382.48  3818.95  27  good
chromium@435082  5222.74  3676.13  27  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 671233

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests startup.cold.blank_page
Test Metric: first_main_frame_load_time/first_main_frame_load_time
Relative Change: 2.97%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1969
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994097642836391168


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

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

Ref build results moved at the same time.

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : first_main_frame_load_time/first_main_frame_load_time

Revision             Result                  N
chromium@434982      5056.71 +- 4046.08      21      good
chromium@435082      5227.62 +- 4259.45      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 startup.cold.blank_page

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

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


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