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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : page_cycler_v2.intl_ar_fa_he
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.google.com.sa_

Revision             Result                  N
chromium@459783      73.6597 +- 48.6098      21      good
chromium@459889      65.705 +- 22.4718       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.google.com.sa. page_cycler_v2.intl_ar_fa_he

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

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


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

=== 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: mac_retina_perf_bisect
  Benchmark    : page_cycler_v2.intl_ar_fa_he
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/http___www.google.com.sa_
  Change       : 11.74% | 73.9194285703 -> 65.2396428585

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/d3d9942bf9942c2e86b4efcd2100fefb1a74e078..09812d36f72be34ba5e68441222750b4b0a6b3a9


Revision             Result                  N
chromium@459783      73.9194 +- 41.1552      21       good
chromium@459837      72.9226 +- 27.1862      14       good
chromium@459851      71.8151 +- 24.4327      14       good
chromium@459854      73.5048 +- 24.8257      6        good
chromium@459855      76.5442 +- 21.3818      6        good
chromium@459856      ---                     ---      build failure
chromium@459857      ---                     ---      build failure
chromium@459858      ---                     ---      build failure
chromium@459859      63.0273 +- 11.228       9        bad
chromium@459863      63.3298 +- 15.1528      14       bad
chromium@459889      65.2396 +- 22.1476      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.google.com.sa. page_cycler_v2.intl_ar_fa_he

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

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


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