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

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


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

android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8:execute_max/total:500ms_window:renderer_eqt:v8:execute_max


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 v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

I'm not sure this is a real regression. cbruni@ please check and either mark as WontFix or assign to someone in that area for investigation.

The ref builds went up as well, so WontFix, similar to  issue 769227