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

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


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

android-one

Started wider bisect.

Could this be https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+/b3e03f627f8f905a5ed63725c07f615dc1389eac ?

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

Telemetry test is failing during bisect: see bug 627786.

I think it is likely to be the tear-down page set CL though. Ned, any thoughts? I think Juan is on vacation.

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+/b3e03f627f8f905a5ed63725c07f615dc1389eac definitely will cause some regression, but it should cause regression across the board. All page cycler benchmarks has pageset_repeat option set to 6, so it seems fishy that only  page_cycler.top_10_mobile regressed by 13.6%.

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

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@403831  5291.27  147.542  9  good
chromium@403839  5222.11  115.989  8  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 627086

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

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


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

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

The bisect can't reproduce this & ref build's metric also jump around the same time in https://chromeperf.appspot.com/group_report?bug_id=627086, so I would say this is due to some hardware change.


Please reopen if you don't agree with this assessment.