Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

This is another case where Skia is asserting on things that don't cause security issues, just maybe unexpected results / user issues.  This is just an assert on SkRRect validity for ovals, and if I remove those asserts, there is no underlying bug here.

I am going to WontFix this.

ClusterFuzz has detected this issue as fixed in range 609963:609968.

Detailed report: https://clusterfuzz.com/testcase?key=6666366820810752

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x05390014e858
Crash State:
  sk_abort_no_print
  SkRRect::setOval
  SkRRect::setOval
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=555638:555648
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=609963:609968

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6666366820810752

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.