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

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


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

chromium-rel-mac11

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

=== 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_10_11_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/24h
  Change       : 10.79% | 188.314380935 -> 167.991285707

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/2fde6d35bd484cc0cb9a4b7964f0a5e2cf000a6a..8aebbaa46a1af6f69ae64005cc7c04da4c367547


Revision             Result                  N
chromium@474979      188.314 +- 45.7635      21       good
chromium@475015      188.384 +- 56.6628      14       good
chromium@475025      188.991 +- 8.26789      9        good
chromium@475029      185.104 +- 33.407       14       good
chromium@475030      ---                     ---      build failure
chromium@475031      171.335 +- 65.3992      14       bad
chromium@475033      168.779 +- 77.0718      14       bad
chromium@475051      171.239 +- 36.3639      14       bad
chromium@475122      167.991 +- 78.1212      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=24h loading.desktop

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

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


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