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

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

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

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


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

=== 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.0592524 +- 0.0171176      6      good
chromium@464604      0.0561133 +- 0.0001221      6      good
chromium@464605      15.1374 +- 0.862474         6      bad       <--
chromium@464606      14.9966 +- 1.63256          6      bad
chromium@464608      15.0899 +- 0.501199         6      bad
chromium@464612      15.1827 +- 0.481571         6      bad
chromium@464618      15.0111 +- 1.395            6      bad
chromium@464631      14.7719 +- 1.0762           6      bad
chromium@464658      14.8892 +- 0.848708         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/8981959869619048096

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


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