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

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


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

chromium-rel-mac11

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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : page_cycler_v2.typical_25
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.theonion.com

Revision             Result                  N
chromium@459263      310.593 +- 84.8492      21      good
chromium@459363      312.488 +- 74.3013      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...www.theonion.com page_cycler_v2.typical_25

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

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


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

data get to be the same level to the previous good revisions in the later revisions. so close as wontfix.