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

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


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

android-webview-nexus5X

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

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

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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/blank.html


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=blank.html thread_times.key_idle_power_cases

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

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


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

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

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

Suspected Commit
  Author : mlippautz
  Commit : f86985ad116d75255ddf78b3a4df2590543fd8cd
  Date   : Wed May 10 15:30:36 2017
  Subject: [heap] Bound number of tasks by embedder limit instead of artificially capping

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/blank.html
  Change       : 11.33% | 2.92994702257 -> 3.26176941652

Revision                           Result                    N
chromium@471270                    2.92995 +- 0.0583388      6      good
chromium@471278                    2.95434 +- 0.0835467      6      good
chromium@471280                    2.92977 +- 0.135807       6      good
chromium@471280,v8@5c66d6fcd4      2.90404 +- 0.178678       6      good
chromium@471280,v8@cf37556f0e      2.92988 +- 0.0563524      6      good
chromium@471280,v8@69c6970fae      2.90447 +- 0.044984       6      good
chromium@471280,v8@2026d5cb79      2.92147 +- 0.059942       6      good
chromium@471280,v8@11a211ff1b      2.91306 +- 0.0583407      6      good
chromium@471280,v8@f86985ad11      3.22883 +- 0.114659       6      bad       <--
chromium@471281                    3.20498 +- 0.0469998      6      bad
chromium@471282                    3.2296 +- 0.0902297       6      bad
chromium@471286                    3.26177 +- 0.057702       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=blank.html thread_times.key_idle_power_cases

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

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


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