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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e1bef6c99fa9d0ca3789763a80e0c76310bf6831 (cc: Add PaintOp fuzzer for serialization equality).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

I don't think it's worth fixing every assert in Skia unless it causes a real issue in a release build.

ClusterFuzz testcase 5478638991704064 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 530630:530658.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900007175
Crash State:
  sk_abort_no_print
  SkRRect::computeType
  SkRRect::computeType
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=520313:520368
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=530630:530658

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

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.