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

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


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

win-zenbook

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

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

Bisect Details
  Configuration: winx64_zen_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstMeaningfulPaint_avg/load_games/load_games_spychase

Revision             Result                  N
chromium@451767      704.388 +- 70.3934      21      good
chromium@451852      704.102 +- 63.1635      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.games.spychase system_health.common_desktop

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

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


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

Looks like this test is noisy. I probably should have realized this before kicking-off this bug and bisects.