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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=ab9c7b5ab83fa2e3abc0aeddfd045c41aae765fc509fd7fd615ed3eee1c3546e


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Stroke Shapes

Revision             Result                  N
chromium@510668      49.9013 +- 1.77245      21      good
chromium@510708      49.901 +- 1.23363       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=MotionMark.Canvas.Stroke.Shapes smoothness.gpu_rasterization.tough_path_rendering_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8964860602079893328


For feedback, file a bug with component Speed>Bisection

ref build moved too.