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

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


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

chromium-rel-mac11
chromium-rel-mac12-mini-8gb

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 91509778fd90e0964f86fa683b4dd4224cc8d3fe
  bad_revision : f5ec8bec81e8f54e11e0367836294357dd99c915

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/24h

Revision             Result                  N
chromium@478849      1521.34 +- 799.369      14       good
chromium@478894      ---                     ---      build failure
chromium@478895      1280.44 +- 1674.08      21       bad
chromium@478939      1290.54 +- 1937.71      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/8976709545741815696

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


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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 91509778fd90e0964f86fa683b4dd4224cc8d3fe
  bad_revision : 239d4798dfeee56d5b6feb44060a086c88e00557

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/24h

Revision             Result                  N
chromium@478849      1454.56 +- 1691.48      21      good
chromium@478894      1214.81 +- 1968.81      21      bad
chromium@478939      1329.87 +- 1298.31      20      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/8976687254942228464

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


| 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 came back down a few revisions later.