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

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


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

linux-release

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

Hi kbr@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Delete bogus telemetry_gpu_new_test_run target.
Author  : kbr
Commit description:
  
BUG= 585495 
TBR=jmadill@chromium.org, geofflang@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/1685853002

Cr-Commit-Position: refs/heads/master@{#374479}
Commit  : 24bc5b8232c660178219ef88c47151c7e33b3252
Date    : Tue Feb 09 21:51:17 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@374392         52.655042   0.458142    8           good
chromium@374436         52.768017   0.673645    8           good
chromium@374458         52.90129    0.50075     8           good
chromium@374469         52.933622   0.46961     8           good
chromium@374475         52.9604     0.609779    7           good
chromium@374478         53.110995   0.302384    8           good
chromium@374479         53.898894   0.59151     8           bad
chromium@374480         53.891939   0.300875    8           bad

Bisect job ran on: linux_perf_bisect
Bug ID: 590793

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests media.tough_video_cases
Test Metric: energy_consumption_mwh/energy_consumption_mwh
Relative Change: 2.07%
Score: 99.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6250
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9019459445214927792


| 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 label Cr-Tests-AutoBisect.  Thank you!

Sorry, all my CL did was delete a bogus build target. It didn't affect the binaries in any way and there's no way it could have caused this regression.

jrummell: please check the ref build on the graph before filing. In this case, the ref build jumped at the same time as the ToT, which means something about the machine or the test changed, not Chrome. The dashboard tries to not alert if the ref build jumped like this, but sometimes it can get confused by noise.

kbr: sorry for the noise here.

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

Hi nasko@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Add methods to NavigationHandle to allow refactoring webNavigation to use it.
Author  : nasko
Commit description:
  
The webNavigation API is currently using WebContentsObserver APIs based
on RenderFrameHost. Both Site Isolation and PlzNavigate are changing how
navigation behaves and the latter requires the observers to move to use
the NavigationHandle API. However, the webNavigation code requires
functionality which isn't currently present and this CL adds that.

The refactoring of webNavigation to use the methods added in this CL is in https://codereview.chromium.org/1670673003.
BUG= 532666 ,  584493 
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

Review URL: https://codereview.chromium.org/1667163002

Cr-Commit-Position: refs/heads/master@{#374478}
Commit  : 918f1d4c00f6bb2f757e80af118f1785bd333ecf
Date    : Tue Feb 09 21:51:16 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@374392         54.891837   0.60108     8           good
chromium@374436         55.041199   0.802705    8           good
chromium@374458         54.961903   0.630182    8           good
chromium@374469         54.493536   0.557029    41          good
chromium@374475         54.690751   0.509869    41          good
chromium@374477         54.583476   0.261423    8           good
chromium@374478         53.920102   0.298642    5           bad
chromium@374480         54.307974   0.603024    27          bad

Bisect job ran on: linux_perf_bisect
Bug ID: 590793

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --also-run-disabled-tests media.tough_video_cases
Test Metric: energy_consumption_mwh/energy_consumption_mwh
Relative Change: 1.24%
Score: 99.5

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6251
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9019459421599246368


| 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 label Cr-Tests-AutoBisect.  Thank you!