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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Fill Shapes

Revision             Result                  N
chromium@473875      59.9977 +- 3.50975      21      good
chromium@473895      60.0052 +- 2.70927      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=MotionMark.Canvas.Fill.Shapes smoothness.gpu_rasterization.tough_path_rendering_cases

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

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


| 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/8978616214059468144

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Fill Shapes
  Change       : 1.30% | 60.2014212233 -> 59.4418757872

Suspected Commit Range
  7 commits in range
  https://chromium.googlesource.com/chromium/src/+log/537653e94532216958db3c24c573c6f833cdbcbf..1705541fd8c739910905d53ad30c40c41b59a25d


Revision             Result                  N
chromium@473875      60.2014 +- 2.40085      14       good
chromium@473877      60.2445 +- 2.56707      14       good
chromium@473878      ---                     ---      build failure
chromium@473879      ---                     ---      build failure
chromium@473880      ---                     ---      build failure
chromium@473881      ---                     ---      build failure
chromium@473882      ---                     ---      build failure
chromium@473883      ---                     ---      build failure
chromium@473884      59.49 +- 2.19534        14       bad
chromium@473895      59.4419 +- 1.92582      14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=MotionMark.Canvas.Fill.Shapes smoothness.gpu_rasterization.tough_path_rendering_cases

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

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


| 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/8976998842400349728

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Fill Shapes
  Change       : 1.89% | 59.3479662442 -> 60.4678829705

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/b5bc34bb90fbc11a76389cc67330ec1fb4e78176..6b86d7c8b20f25282abef00a275c40ced632aab4


Revision             Result                  N
chromium@473000      59.348 +- 2.49506       14       good
chromium@473001      ---                     ---      build failure
chromium@473002      60.1376 +- 2.49158      14       bad
chromium@473003      60.0852 +- 1.82295      14       bad
chromium@473006      59.9941 +- 1.60733      14       bad
chromium@473013      60.0998 +- 2.84623      14       bad
chromium@473025      60.1233 +- 2.42112      14       bad
chromium@473050      59.9852 +- 3.22318      21       bad
chromium@473100      59.978 +- 2.87959       14       bad
chromium@473200      60.3842 +- 2.2674       9        bad
chromium@473400      60.4679 +- 3.48849      14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=MotionMark.Canvas.Fill.Shapes smoothness.gpu_rasterization.tough_path_rendering_cases

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

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


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

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