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

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


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

android-one

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1735
Failure reason: the build has failed due to infrastructure failure.

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

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


===== SUSPECTED CL(s) =====
Subject : Add a console messsage for HTTP-bad
Author  : estark
Commit description:
  
This CL logs a console message (at most once per navigation) when
ChromeSecurityStateModelClient::GetSecurityInfo() returns a security
level of HTTP_SHOW_WARNING. This message will allow us to start testing
when password/credit card detection will trigger a "Not secure" warning
in the omnibox, and will allow developers to start testing their sites.

BUG= 647561 
TEST=In chrome://flags, set #mark-non-secure-as to "Display a verbose
state when password or credit card fields are detected on an HTTP
page". Visit an HTTP page with a password field, like
http://nytimes.com. Open Developer Tools and observe a warning message
about the "Not secure" warning in the console.

Review-Url: https://codereview.chromium.org/2410043003
Cr-Commit-Position: refs/heads/master@{#425739}
Commit  : f8b269e58af3d7413986fb3196ce9e3f2d67a72f
Date    : Mon Oct 17 19:22:46 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@425738  1781760  0.0      5  good
chromium@425739  1806336  0.0      5  bad    <--
chromium@425740  1806336  0.0      5  bad
chromium@425741  1806336  0.0      5  bad
chromium@425744  1806336  0.0      5  bad
chromium@425749  1806336  0.0      5  bad
chromium@425759  1806336  0.0      5  bad
chromium@425779  1806336  0.0      5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 657536

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.en.m.wikipedia.org.wiki.Science memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
Relative Change: 1.38%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1747
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998224393153439024


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5847668633370624

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