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

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


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

android-nexus5

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

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

=== 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       : timeToFirstMeaningfulPaint_avg/load_news/load_news_nytimes
  Change       : 53.68% | 1229.25433333 -> 569.411833333

Revision             Result                  N
chromium@470444      1229.25 +- 146.137      6      good
chromium@470473      1200.41 +- 400.069      6      good
chromium@470487      1234.93 +- 261.118      6      good
chromium@470489      1239.11 +- 187.459      6      good
chromium@470490      571.242 +- 34.8935      6      bad       <--
chromium@470491      577.378 +- 46.3144      6      bad
chromium@470494      569.186 +- 55.8208      6      bad
chromium@470501      569.412 +- 54.482       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/8979553849602167824

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


| 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       : timeToFirstMeaningfulPaint_avg/load_news/load_news_nytimes
  Change       : 53.76% | 1184.62111111 -> 547.807

Revision             Result                  N
chromium@470444      1184.62 +- 727.306      9      good
chromium@470473      1258.23 +- 55.4569      6      good
chromium@470487      1001.82 +- 711.29       6      good
chromium@470489      1246.79 +- 77.8688      6      good
chromium@470490      571.915 +- 30.3776      6      bad       <--
chromium@470491      533.872 +- 119.353      6      bad
chromium@470494      555.183 +- 41.0233      6      bad
chromium@470501      547.807 +- 165.771      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/8979553840866263312

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


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