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

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


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

win-zenbook

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/load_social/load_social_pinterest

Revision             Result                  N
chromium@442772      1321.99 +- 316.697      21      good
chromium@442831      1391.44 +- 490.249      21      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=load.social.pinterest system_health.common_desktop

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

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


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

Recovered.

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