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

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


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

win-zenbook

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

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

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/browse_news/browse_news_nytimes

Revision             Result                  N
chromium@442563      1103.19 +- 413.901      21      good
chromium@442661      1150.02 +- 450.663      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=browse.news.nytimes system_health.common_desktop

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

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


| 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