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

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


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

android-nexus5

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

=== 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_social/load_social_facebook
  Change       : 40.67% | 1079.83077778 -> 640.643666667

Revision             Result                  N
chromium@470444      1079.83 +- 541.264      9       good
chromium@470473      1008.67 +- 596.658      9       good
chromium@470487      1015.04 +- 775.665      14      good
chromium@470489      1119.46 +- 56.0097      6       good
chromium@470490      618.088 +- 46.8241      6       bad       <--
chromium@470491      634.171 +- 79.9871      9       bad
chromium@470494      630.354 +- 112.825      6       bad
chromium@470501      640.644 +- 155.31       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.social.facebook system_health.common_mobile

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

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


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