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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : page_cycler_v2.typical_25
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.fifa.com_

Revision             Result                  N
chromium@458738      1684.52 +- 2392.88      21      good
chromium@458999      1617.1 +- 1462.41       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=http...www.fifa.com. page_cycler_v2.typical_25

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

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


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