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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx9H9sAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx_uYoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgh6_sqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx_CPpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx73XrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgh4-GrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx72jtAoM


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

chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

===== 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@435010  781.619  2339.37  27  good
chromium@435082  688.87   151.021  27  bad

Bisect job ran on: win_perf_bisect
Bug ID: 670331

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...zol.com.cn. page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstContentfulPaint_avg/pcv1-cold/http___zol.com.cn_
Relative Change: None

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


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

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : page_cycler_v2.intl_ja_zh
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___zol.com.cn_

Revision             Result                  N
chromium@435010      816.234 +- 2117.04      21      good
chromium@435082      681.167 +- 22.4432      21      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=http...zol.com.cn. page_cycler_v2.intl_ja_zh

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

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


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

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