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

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


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

chromium-rel-mac11
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : page_cycler_v2.intl_ar_fa_he
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.aljayyash.net_

Revision             Result                  N
chromium@462011      137.196 +- 80.8677      21      good
chromium@462064      158.389 +- 94.6941      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.aljayyash.net. page_cycler_v2.intl_ar_fa_he

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : page_cycler_v2.intl_ar_fa_he
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.aljayyash.net_
  Change       : 21.46% | 135.363428571 -> 164.406785714

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/8bd5d6a15f00ab291c675c2e49b19275d263b6bc..ef483ecbe4cfa6e394aa01205a51e5fac19fb2ab


Revision             Result                  N
chromium@462011      135.363 +- 61.8598      14       good
chromium@462018      137.126 +- 79.9397      14       good
chromium@462020      138.921 +- 73.9348      14       good
chromium@462021      ---                     ---      build failure
chromium@462022      ---                     ---      build failure
chromium@462023      ---                     ---      build failure
chromium@462024      164.384 +- 52.8071      14       bad
chromium@462037      164.367 +- 70.5373      14       bad
chromium@462064      164.407 +- 61.9381      14       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.aljayyash.net. page_cycler_v2.intl_ar_fa_he

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

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


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