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

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


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

android-nexus6

=== Auto-CCing suspected CL author catapult-deps-roller@chromium.org ===

Hi catapult-deps-roller@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 : Roll src/third_party/catapult/ 973a51b36..da95c544e (1 commit).
Author  : catapult-deps-roller
Commit description:
  
https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/973a51b36f5e..da95c544ec76

$ git log 973a51b36..da95c544e --date=short --no-merges --format='%ad %ae %s'

CQ_INCLUDE_TRYBOTS=
TBR=catapult-sheriff@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#381897}
Commit  : 25a21b4f8b405ba32d8cc31f1934bbd89a1afd48
Date    : Fri Mar 18 05:44:12 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@381884         1369.162685 20.327543   6           good
chromium@381892         1361.358278 26.055434   5           good
chromium@381896         1361.483556 17.956603   5           good
chromium@381897         1578.375222 49.150501   5           bad
chromium@381898         1586.891667 43.007545   5           bad
chromium@381900         1552.327889 41.084974   5           bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 596169

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests page_cycler.top_10_mobile
Test Metric: warm_times/page_load_time
Relative Change: 13.29%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2029
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017820153038326496


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

The only thing in the catapult roll is https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+/da95c544ec7607e8657a30bce94f14d6fb645636.

Ned, does this regression make sense? Where reference builds exist, it looks like they regressed as well, so this is probably WontFix.

Yes. Because fake certificate no longer works on Android M, we now use "--enable-certicate-error" which will make chrome pops up a warning butter bar when Chrome navigate to https site. Since page-cyler is mostly around page load time, this regression is expected.


+Kouhei: something to be aware of.

@ned,

We can add support for bisecting into catapult rolls, but we'll need you to make 'catapult_revision' a part of the vars dict in the DEPS file.

Does it make sense to do it?

Oops, commented on the wrong bug.