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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-cold/http___amarchoti.blogspot.com

Revision             Result                  N
chromium@453166      1632.43 +- 1575.56      21      good
chromium@453202      1669.76 +- 1297.9       19      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 --story-filter=http...amarchoti.blogspot.com page_cycler_v2.tough_layout_cases

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

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


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