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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : transform-changes/transform-changes

Revision             Result                  N
chromium@455055      218.155 +- 31.3676      21      good
chromium@455132      218.443 +- 49.4657      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 blink_perf.paint

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

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


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

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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.