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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : media.android.tough_video_cases
  Metric       : application_energy_consumption_mwh/video.html?src_crowd1080_vp9.webm_canvas_true

Revision             Result                  N
chromium@455113      12.5703 +- 8.76783      21      good
chromium@455178      12.7759 +- 8.85039      21      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=video.html.src.crowd1080.vp9.webm.canvas.true media.android.tough_video_cases

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

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


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

As mentioend in Comment #0, this regression is really restoring to the original value after a temporary dip. Dip looked pretty suspicious (graph seems to oscillate between pre/post dip values now), and bisect doesn't repro the result - likely noise.