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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggfr0twoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggaD3uwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggZSqjggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_rnSqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwY-XvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggfLxugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgweSEpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_o_Y5AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_smJ-AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_uy0uQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_vipvAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_o-CtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggbLTrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvs37vAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_t2tvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_uv9uAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_vrAtQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvtzn7goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICggYLGpgoM


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

android-nexus5
chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11
chromium-rel-win10
chromium-rel-win7-dual

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

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

kouhei: r414568 is in the range:
[PCv2] Enable toplevel tracing category

Is this expected?

This appears to have recovered as per the graphs, so I think we can probably wontfix?

Yes. This is expected. Thanks so much for checking the CL range.

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : page_cycler_v2.typical_25
  Metric       : pcv1-cold-timeToFirstContentfulPaint_avg/http___www.fda.gov


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.typical_25

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982647700619967968

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5240275776045056


| 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 Speed>Bisection.  Thank you!