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

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


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

android-webview-nexus6

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : node-type/node-type

Revision             Result                  N
chromium@477251      223.077 +- 43.9526      21      good
chromium@477265      221.091 +- 40.7655      21      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 blink_perf.bindings

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

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


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

 Issue 730540  has been merged into this issue.

This recovered.