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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-one
android-webview-nexus5X
android-webview-nexus6

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : blink_perf.parser
  Metric       : html5-full-render/html5-full-render

Revision             Result              N
chromium@512781      49418.0 +- 0.0      1      good

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-chromium --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/8963934067365180240


For feedback, file a bug with component Speed>Bisection

Recovered.