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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvq2TtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_syMrQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_tP0ogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvo2vsAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_rXrqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggciMpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvsn_vwsM


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

android-galaxy-s5
android-nexus5
chromium-rel-mac-hdd
chromium-rel-mac10
linux-release

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/965
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/9002981412508020096

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

kouhei@: There are quite a few big regressions in page_cycler_v2 recently, and bisects are always failing to find the cause(s). I am assigning the bugs to you since you seem to have made many (most?) PCv2 changed recently. If I am wrong, could you please help me find the right owner of these bugs?

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

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

Hi kouhei@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 : Introduce PageCyclerStory and let the stories wait for onload+TTI
Author  : kouhei
Commit description:
  
BUG= 626274 

Review-Url: https://codereview.chromium.org/2244943002
Cr-Commit-Position: refs/heads/master@{#413414}
Commit  : 5cbfbf15751cfaff33008bd0dd54699b7791158b
Date    : Mon Aug 22 07:10:47 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@413405  153.257  2.73611  5  good
chromium@413410  152.23   6.48561  5  good
chromium@413412  154.315  4.79748  5  good
chromium@413413  181.681  62.6847  5  good
chromium@413414  461.63   18.8906  5  bad    <--

Bisect job ran on: linux_perf_bisect
Bug ID: 641495

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.intl_es_fr_pt-BR
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.voila.fr_
Relative Change: 201.21%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6723
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000723249222065152


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

| 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. The CL is the change to pcv2 itself, and ttFMP before the CL was incorrect.