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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgo6bzrgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgo4jRsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgo4OpqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgw_6y8goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgo-aHjAgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgw92stgsM


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

android-nexus5
android-nexus6
android-nexus7v2
android-nexus9

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

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


===== SUSPECTED CL(s) =====
Subject : [loading metric] filter out events during cache warming
Author  : ksakamoto
Commit description:
  
The regexp in prepareTelemetryInternalEventPredicate did not match
the titles of events logged by cache_temperature.py.

Note for perf sheriffs: Improvements are expected in page_cycler_v2
benchmarks.

BUG=catapult:#2962

Review-Url: https://codereview.chromium.org/2467763002
Commit  : 0d3575d73a471a53e1d1d363a349ad4536f293fc
Date    : Tue Nov 01 12:17:02 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N  Good?
chromium@428990                      534.252  78.5504  5  good
chromium@428992                      899.063  477.73   8  good
chromium@428992,catapult@0d3575d73a  1171.61  284.69   8  bad    <--
chromium@428993                      1208.4   256.392  5  bad
chromium@428994                      1188.11  338.185  5  bad
chromium@428998                      1216.01  254.433  5  bad
chromium@429006                      1158.08  252.806  5  bad
chromium@429021                      1118.91  277.497  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 661542

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_ar_fa_he
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___www.masrawy.com_
Relative Change: 109.43%
Score: 80.0

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


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

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

This is expected. Before my change, pcv1-warm metrics were confused by cache-warming navigations.

 Issue 661932  has been merged into this issue.