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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : jetstream
  Metric       : Score/Score

Revision             Result                  N
chromium@471248      164.492 +- 1.60686      21      good
chromium@471297      164.159 +- 1.92175      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 jetstream

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

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


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

=== 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    : jetstream
  Metric       : Score/Score
  Change       : 0.48% | 164.857142857 -> 164.071428571

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/2f149a05d31ad319ef6b620911b74e390dbee354..4d83ef17a6e7f586f32f7c894e0bb11187c72a8d


Revision             Result                   N
chromium@471248      164.857 +- 3.04464       14       good
chromium@471273      164.833 +- 1.98606       14       good
chromium@471279      164.833 +- 1.87083       14       good
chromium@471280      164.944 +- 0.871355      6        good
chromium@471281      ---                      ---      build failure
chromium@471282      ---                      ---      build failure
chromium@471283      164.175 +- 2.89133       21       bad
chromium@471286      164.238 +- 2.16758       21       bad
chromium@471297      164.071 +- 1.71131       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 jetstream

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

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


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