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

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


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

android-nexus9

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2106
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2108
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2109
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

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


===== SUSPECTED CL(s) =====
Subject : [Telemetry] Switch ShouldTearDownStateAfterEachStoryRun to True as default
Author  : perezju
Commit description:
  
To reduce complexity of benchmarks and imcrease stability of measurements
benchmarks will now tear down the state (i.e. restart the browser) between
each page/story of a test.

Perf sherfiffs warning: This CL is expected to affect measurements of
many benchmarks.

BUG= chromium:640990 

Review-Url: https://codereview.chromium.org/2304893002
Commit  : 4f812c9035e6cf9bad6774bb6ff71c1822167e0a
Date    : Sat Sep 03 10:45:26 2016


===== TESTED REVISIONS =====
Revision                             Mean     Std Dev  N  Good?
chromium@416436                      240.8    5.19684  5  good
chromium@416447                      242.348  11.2911  5  good
chromium@416452                      237.944  5.21013  8  good
chromium@416452,catapult@4f812c9035  362.839  38.7437  5  bad    <--
chromium@416453                      384.443  131.455  9  bad
chromium@416454                      414.602  112.141  8  bad
chromium@416455                      348.638  46.3474  5  bad
chromium@416457                      341.842  28.3124  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 646141

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.top_10_mobile
Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___yandex.ru_touchsearch?text_science
Relative Change: 41.96%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2144
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999799900588030720


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

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

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

Bisect failed: None
Failure reason: incorrect bisect configuation.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

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

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

Bisect failed: None
Failure reason: incorrect bisect configuation.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Bisect failed: None
Failure reason: incorrect bisect configuation.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.