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

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


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

chromium-rel-mac11-pro

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB

Revision             Result                  N
chromium@480312      116.833 +- 22.3663      21      good
chromium@480326      113.893 +- 17.1314      21      unknown
chromium@480339      112.327 +- 10.9155      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=IMDB loading.desktop

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

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


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

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

The bisect was able to narrow the range, you can try running with:
  good_revision: add3c68a6c8aea99a4f7088193f99d5eaaa5b510
  bad_revision : 84047549ac37bab70d7306566c912e59131f3e1f

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


Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB
  Change       : 7.70% | 113.689777778 -> 122.445166667

Revision             Result                  N
chromium@480312      113.69 +- 11.8383       9       good
chromium@480328      113.938 +- 8.37105      9       good
chromium@480336      115.443 +- 13.3352      9       good
chromium@480340      114.638 +- 15.4865      14      good
chromium@480342      121.808 +- 11.241       9       bad
chromium@480343      124.144 +- 13.2468      9       bad
chromium@480374      123.768 +- 9.90554      6       bad
chromium@480436      122.445 +- 11.9491      6       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=IMDB loading.desktop

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Yutaka Hirano
  Commit : 84047549ac37bab70d7306566c912e59131f3e1f
  Date   : Mon Jun 19 04:16:15 2017
  Subject: [Loading] Save one post-task when the data pipe is ready on arrival

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/IMDB
  Change       : 8.84% | 115.164888889 -> 125.346666667

Revision             Result                  N
chromium@480312      115.165 +- 15.033       9       good
chromium@480328      114.509 +- 13.9013      9       good
chromium@480336      114.512 +- 13.977       9       good
chromium@480340      114.2 +- 8.84307        9       good
chromium@480341      115.221 +- 15.657       14      good
chromium@480342      123.116 +- 11.4619      9       bad       <--
chromium@480343      125.206 +- 11.2398      9       bad
chromium@480374      127.744 +- 4.01495      6       bad
chromium@480436      125.347 +- 6.87403      6       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=IMDB loading.desktop

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

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


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