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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8a_tpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiZTMuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8Z_NsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgib7yvQkM


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

chromium-rel-mac10
chromium-rel-win10
linux-release
win-zenbook

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/713
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/8999798449993651056

=== Auto-CCing suspected CL author perezju@chromium.org ===

Hi perezju@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 : [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@416451                      204.2    26.8965  5  good
chromium@416452                      204.184  10.5109  5  good
chromium@416452,catapult@4f812c9035  566.09   61.2331  5  bad    <--
chromium@416453                      504.144  62.7345  5  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 645315

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_es_fr_pt-BR
Test Metric: timeToFirstContentfulPaint_avg/pcv1-cold/http___www.leboncoin.fr_annonces_offres_limousin_
Relative Change: 146.89%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/734
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999798449993651056


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

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

FYI: Not a real regression, but measurements go up as we now restart the browser between individual stories. So this is basically the difference between a cold/warm start.