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

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


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

android-nexus5X

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

=== 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    : webrtc.peerconnection
  Metric       : cpu_utilization/720p_call_45s


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 webrtc.peerconnection

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

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


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

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

Suspected Commit
  Author : dfalcantara
  Commit : 8ef9faffba78738c37df77a160fea80ee5f604af
  Date   : Thu Apr 13 23:30:05 2017
  Subject: 🔍 Update how shared preferences are handled by the widget

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : webrtc.peerconnection
  Metric       : cpu_utilization/720p_call_45s

Revision             Result                      N
chromium@464549      0.0529951 +- 0.0315423      6      good
chromium@464604      0.0529654 +- 0.017032       6      good
chromium@464605      15.1145 +- 0.636487         6      bad       <--
chromium@464606      15.2688 +- 0.431702         6      bad
chromium@464608      15.1283 +- 0.901962         6      bad
chromium@464611      15.1705 +- 0.82611          6      bad
chromium@464618      14.7716 +- 1.07039          6      bad
chromium@464631      15.0619 +- 0.783995         6      bad
chromium@464658      15.0032 +- 1.12252          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 webrtc.peerconnection

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

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


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