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

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


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

android-nexus5

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

=== 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    : v8.runtimestats.browsing_mobile_classic
  Metric       : V8 C++:duration_avg/browse_chrome/browse_chrome_newtab
  Change       : 36.29% | 3126.13766667 -> 1991.55933333

Revision             Result                  N
chromium@470442      3126.14 +- 397.084      6      good
chromium@470467      3181.19 +- 323.56       6      good
chromium@470480      3127.38 +- 343.207      6      good
chromium@470486      3084.67 +- 332.196      6      good
chromium@470489      3231.87 +- 78.9888      6      good
chromium@470490      2149.91 +- 1356.32      6      bad       <--
chromium@470491      2260.97 +- 975.763      6      bad
chromium@470492      1991.56 +- 1056.95      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=browse.chrome.newtab v8.runtimestats.browsing_mobile_classic

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

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


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