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

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


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

chromium-rel-win7-dual

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

===== BISECT JOB RESULTS =====
Status: failed


=== 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.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@430600  N/A   N/A      0  good
chromium@430651  N/A   N/A      0  bad

Bisect job ran on: win_perf_bisect
Bug ID: 664480

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests startup.warm.blank_page
Test Metric: first_main_frame_load_time/first_main_frame_load_time
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/7043
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8996290481956402800


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

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

Triggered job in staging to test:

http://build.chromium.org/p/tryserver.chromium.perf/builders/staging_win_perf_bisect/builds/48

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

robertocn: Above try-job failed with a 500 error while trying to post the result. Not sure if this was expected since it was in staging? The JSON output suggests the bisect failed anyway.

The 500 error sounds like  bug 664512 .

Looking at the bisect output, we're having problems reading the output of startup benchmarks on Windows.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build.git/+/3aa5fb04713bc29c601c93c05414ed4b0214c15f

commit 3aa5fb04713bc29c601c93c05414ed4b0214c15f
Author: Roberto Carrillo <robertocn@google.com>
Date: Tue Nov 15 18:54:18 2016

Pushing the following two changes to production.

https://chromium-review.googlesource.com/#/c/411403/
https://chromium-review.googlesource.com/#/c/411421/

R=stip@chromium.org,sullivan@chromium.org
BUG= 664480 ,660852

Change-Id: I1cf4ca4557257ad1784dc4b5d48db6134134eb7d
Reviewed-on: https://chromium-review.googlesource.com/411452
Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
Reviewed-by: Mike Stipicevic <stip@chromium.org>

[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipe_modules/auto_bisect/api.py
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipe_modules/auto_bisect/bisector.py
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/basic_perf_tryjob_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/basic_perf_tryjob_with_metric_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/basic_perf_tryjob_with_revisions_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/basic_recipe_android_webview_arm64_aosp_perf_bisect.json
[rename] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/local_basic_recipe_disconnected_device.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/perf_cq_no_benchmark_to_run_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/perf_cq_no_changes_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/perf_cq_run_benchmark_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/perf_tryjob_config_error_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.expected/perf_tryjob_failed_test_android_webview_arm64_aosp_perf_bisect.json
[modify] https://crrev.com/3aa5fb04713bc29c601c93c05414ed4b0214c15f/scripts/slave/recipes/bisection/android_bisect.py

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@430600  N/A   N/A      0  good
chromium@430651  N/A   N/A      0  bad

Bisect job ran on: win_perf_bisect
Bug ID: 664480

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests startup.warm.blank_page
Test Metric: first_non_empty_paint_time/first_non_empty_paint_time
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/7048
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995900916447152832


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

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

Roberto, the failure reason listed by bisect on this job is: "Bisect cannot identify a culprit: No values were found while testing the reference range.". But the bug update is super confusing. Was the patch that landed on this bug meant to address that?

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/8982619772944966656

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