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

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


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

android-webview-nexus5X

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

=== 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/8976696744435198976

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


| 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/8976517384294340032

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

Hi delphick@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 : Dan Elphick
  Commit : 95929fd549a3d944f945634fe50391ac4317bdf9
  Date   : Wed Jun 14 08:17:36 2017
  Subject: Limit sending of BeginMainFrameNotExpectedUntil

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       : 7.18% | 2.8965964696 -> 3.10448897717

Revision             Result                    N
chromium@479316      2.8966 +- 0.186067        6      good
chromium@479320      2.87934 +- 0.0581318      6      good
chromium@479322      2.92929 +- 0.195134       6      good
chromium@479323      2.8963 +- 0.0999504       6      good
chromium@479324      3.16325 +- 0.0577587      6      bad       <--
chromium@479331      3.10449 +- 0.131058       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/8976517384294340032

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


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

Looking a the traces it seems this patch just moved some events around a bit and does not constitute an actual regression.

 Issue 733752  has been merged into this issue.