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

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


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

android-webview-nexus5X

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

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

Hi lizeb@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 : Benoit Lize
  Commit : d913be8e7e03161be7a03e2d6039e1632a31a08f
  Date   : Tue Oct 24 13:38:27 2017
  Subject: android: Fix typo in orderfile_generator.py.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : html5-full-render/html5-full-render
  Change       : 0.24% | 18620.1450476 -> 18664.7428095

Revision             Result                  N
chromium@511112      18620.1 +- 208.684      21      good
chromium@511125      18611.5 +- 46.8398      9       good
chromium@511128      22972.2 +- 18518.4      9       good
chromium@511130      29924.1 +- 17267.7      14      good
chromium@511131      18659.6 +- 150.353      9       bad       <--
chromium@511137      18723.3 +- 22.8713      6       bad
chromium@511161      18664.7 +- 162.727      21      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.parser

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

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


For feedback, file a bug with component Speed>Bisection

The CL above fixes a bug in a bot that runs asynchronously every 3h, so a bisect cannot  end up finding a regression caused by this CL.

Re-assigning to brianderson@ for triage.

Graphs have recovered.