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

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


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

android-nexus5

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

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

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

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstContentfulPaint_avg/load_news/load_news_nytimes
  Change       : 55.29% | 1224.55722222 -> 572.206

Revision             Result                  N
chromium@470444      1224.56 +- 493.052      9      good
chromium@470473      1181.0 +- 739.13        9      good
chromium@470487      1146.69 +- 438.924      6      good
chromium@470489      1233.05 +- 166.107      6      good
chromium@470490      534.82 +- 141.603       6      bad       <--
chromium@470491      565.979 +- 15.2765      6      bad
chromium@470494      563.463 +- 37.8681      6      bad
chromium@470501      572.206 +- 56.8268      9      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.nytimes system_health.common_mobile

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

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


| 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 ===
Perf regression found with culprit

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstContentfulPaint_avg/load_news/load_news_nytimes
  Change       : 50.38% | 1164.77566667 -> 577.9195

Revision             Result                  N
chromium@470444      1164.78 +- 473.314      6      good
chromium@470473      1215.08 +- 369.09       6      good
chromium@470487      1182.17 +- 411.948      6      good
chromium@470489      1254.16 +- 132.726      6      good
chromium@470490      564.402 +- 53.3579      6      bad       <--
chromium@470491      574.003 +- 29.8652      6      bad
chromium@470494      555.47 +- 16.5676       6      bad
chromium@470501      577.919 +- 103.069      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.nytimes system_health.common_mobile

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

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


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