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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/load_news/load_news_wikipedia

Revision             Result                 N
chromium@458657      1496.33 +- 1558.2      21      good
chromium@458738      1487.43 +- 1641.9      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.news.wikipedia system_health.common_desktop

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

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


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

loading triage: looks a temporal noise