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

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


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

chromium-rel-win8-dual

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

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

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

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

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

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

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

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

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

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

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

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@416448  231.629  16.2739  18  good
chromium@416451  228.589  3.20796  18  bad

Bisect job ran on: win_8_perf_bisect
Bug ID: 645562

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.top_10_mobile
Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___yandex.ru_touchsearch?text_science
Relative Change: 4.99%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_8_perf_bisect/builds/2219
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001963926368862896


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

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

Perf sheriff fixit: removing owners from bugs owned by the sheriffs who filed them to clarify that the rotation triages the bugs.

Archiving as bisection is difficult and there's been no movement.

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

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

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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : page_cycler_v2.top_10_mobile
  Metric       : pcv1-cold-timeToFirstContentfulPaint_avg/http___yandex.ru_touchsearch?text_science


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

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

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


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

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

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : page_cycler_v2.top_10_mobile
  Metric       : pcv1-cold-timeToFirstContentfulPaint_avg/http___yandex.ru_touchsearch?text_science


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

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

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


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