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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=1b8d7bf0f8d379c69af1a3ca0f984d98fd9dcb1bbd54d85e33ba2330d6ca2c20


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

android-nexus6
android-webview-nexus5X

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

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

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 1fcc2833e80d07d8cc7bb1da734323204527ca56
  bad_revision : 16939e17afbde579a08d22a987c5f379f8875abd

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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstContentfulPaint_avg/hot_Regular-3G/DevOpera

Revision             Result                  N
chromium@505859      2380.64 +- 305.476      6      good
chromium@505953      2319.47 +- 449.081      6      good
chromium@506000      2218.17 +- 323.776      6      good
chromium@506023      2397.25 +- 269.901      6      good
chromium@506035      6938.74 +- 434.54       6      bad
chromium@506046      6674.57 +- 816.199      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=DevOpera loading.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966629817573128032


For feedback, file a bug with component Speed>Bisection

=== Auto-CCing suspected CL author ksakamoto@chromium.org ===

Hi ksakamoto@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Kunihiko Sakamoto
  Commit : b3111d89694181773b830dfebcbc868594cd4be0
  Date   : Tue Oct 03 12:18:52 2017
  Subject: Fix loading metrics after 7c166a82

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstMeaningfulPaint_avg/warm_Regular-3G/FlipBoard
  Change       : 95.22% | 2580.74283333 -> 5038.12216667

Revision                                 Result                  N
chromium@505859                          2580.74 +- 271.722      6      good
chromium@505953                          2687.18 +- 215.466      6      good
chromium@506000                          2593.56 +- 271.057      6      good
chromium@506023                          2636.68 +- 300.862      6      good
chromium@506029                          2598.88 +- 284.466      6      good
chromium@506029,catapult@b3111d8969      4886.07 +- 577.417      6      bad       <--
chromium@506030                          4836.12 +- 288.057      6      bad
chromium@506031                          4897.85 +- 473.452      6      bad
chromium@506032                          4769.71 +- 343.681      6      bad
chromium@506035                          4982.69 +- 510.086      6      bad
chromium@506046                          5038.12 +- 402.834      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=FlipBoard loading.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966606919177578576


For feedback, file a bug with component Speed>Bisection

This is expected. My CL fixed a bug of loading metrics in warm-cache page loads.