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.

It looks like the failure case here of the invalid enum still gets a valid case.  So, I think this is not worth fixing or validating.

ClusterFuzz has detected this issue as fixed in range 578890:578896.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000048e2
Crash State:
  sk_abort_no_print
  to_texture_domain_mode
  SkBlurImageFilterImpl::gpuFilter
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=555645:555651
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=578890:578896

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

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.