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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_bfqpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgg5zguwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgvcfp7ggM


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

win-zenbook

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/573
Failure reason: the build has failed due to infrastructure failure.

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

Bisect bot seems to be green again. Re-running bisect on cleaner test data and w/ wider range...

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

Retrying on narrower range (hopefully w/o a build error).

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/576
Failure reason: the build has failed due to infrastructure failure.

Another one: Each run results in a different "infra failure." Cannot proceed without a successful bisect.

In two of the failures, there is the same infra failure, filed  bug 660841  for it.

In https://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/575 there is no test output. I can't find the stdio of the test. Roberto, can you see the problem here?

These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.

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

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

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : page_cycler_v2.intl_ja_zh
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___www.qq.com_


To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter='http...www\.qq\.com.' page_cycler_v2.intl_ja_zh

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

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


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

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

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

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