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

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


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

android-nexus5

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4106
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/8999798506115321184

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@416436  456.604  58.7566  5  good
chromium@416447  478.818  49.2441  5  good
chromium@416452  514.074  45.501   5  good
chromium@416453  787.553  64.4875  5  bad
chromium@416454  833.841  55.4707  5  bad
chromium@416455  719.889  86.8873  5  bad
chromium@416457  785.052  70.5299  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 645376

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_ja_zh
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-warm/http___zol.com.cn_
Relative Change: 71.93%
Score: 0

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


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

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

Bisect failed to descend into catapult, but r416453 is a catapult roll with just one CL:

2016-09-03 perezju [Telemetry] Switch ShouldTearDownStateAfterEachStoryRun to True as default

Closing as WontFix since this is known to have implications on performance metrics; but assigning to perezju to reopen if this was not expected.

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