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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgho2e5wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-sX2owgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghoi1sAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghojsrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghs7MgAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghvnU_goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tWt-QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-rzU_AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguv_-vgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghv6XugkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuK_pAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuKruQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqHQswkM


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

android-nexus5X
android-nexus6
android-webview-nexus5X
android-webview-nexus6

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : story:power_avg/browse_media/browse_media_imgur


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 --story-filter=browse.media.imgur system_health.common_mobile

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

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


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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : story:power_avg/browse_media/browse_media_imgur


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 --story-filter=browse.media.imgur system_health.common_mobile

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

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


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

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

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : power.typical_10_mobile
  Metric       : energy_consumption_mwh/energy_consumption_mwh


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 power.typical_10_mobile

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

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


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

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

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


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : power.typical_10_mobile
  Metric       : energy_consumption_mwh/energy_consumption_mwh


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 power.typical_10_mobile

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

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


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

Hey Charlie, what do you think's going on here?

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

Kicking off another bisect because the logs from the previous one seem to have expired (?)

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : story:power_avg/browse_shopping/browse_shopping_amazon


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 --story-filter=browse.shopping.amazon system_health.common_mobile

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

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


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

=== Auto-CCing suspected CL author ke.he@intel.com ===

Hi ke.he@intel.com, 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 : Ke He
  Commit : dd2fa336d116912de565aa11f9b916341be3d579
  Date   : Sat May 27 03:04:28 2017
  Subject: Fix the wrong wake lock type in devtools

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : story:power_avg/browse_shopping/browse_shopping_amazon
  Change       : 18.78% | 1.45152963508 -> 1.72409329094

Revision             Result                    N
chromium@475226      1.45153 +- 0.0588734      6      good
chromium@475227      1.45914 +- 0.0792815      6      good
chromium@475228      1.73426 +- 0.0673007      6      bad       <--
chromium@475229      1.71698 +- 0.0366425      6      bad
chromium@475231      1.73779 +- 0.0703654      6      bad
chromium@475235      1.72221 +- 0.0490337      6      bad
chromium@475243      1.72409 +- 0.050547       6      bad

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 --story-filter=browse.shopping.amazon system_health.common_mobile

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

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


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

Hi, Charlie, Sorry I know very little about the run_benchmark test here.
There is an  issue 726290  in which I made a very similar fix. Is it duplicated to this one?

The NextAction date has arrived: 2017-06-12

Thanks for the link to the other bug Ke He! It looks like your "regression" here is actually just fixing the bug introduced in your other CL, as seen on this performance graphs. You can see a graph of the breakage and its revert here: https://chromeperf.appspot.com/group_report?sid=5fe3c7e484ced238e9521e4ea92eaeb75b6f2664cb6254a754ed4e19c21c8668.

Going to go ahead and close this as WontFix.