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

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


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

win-zenbook

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 93bb5a29073d2cb41b20d3cc6cf59459a3906043
  bad_revision : fc599795d2c67209375dddfe4806d9b58a5f1905

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_media/browse_media_youtube

Revision             Result                  N
chromium@456940      1606.82 +- 285.754      6       good
chromium@457007      1663.44 +- 440.542      9       good
chromium@457016      1685.0 +- 286.693       6       good
chromium@457020      15284.4 +- 14711.3      6       bad
chromium@457024      18029.4 +- 350.653      6       bad
chromium@457041      14549.3 +- 25051.6      14      bad
chromium@457074      16238.8 +- 15310.4      9       bad

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=browse.media.youtube system_health.common_desktop

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

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


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

ksakamoto@, does it make sense that https://codereview.chromium.org/2711893002 would have this impact?

Yes.

It seems this benchmark was affected by  bug 659021  and reported FMP too soon.
My change "fixed" this, as it made network-idle window longer.

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