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 suspected regression changelists:

fix running on linux by caryclark@google.com - https://skia.googlesource.com/skia/+/6e64f308910493b4327f7b8aadd7f4aabf3a9601

Fix scaling logic for NexusPlayer and AndroidOne by kjlubick@google.com - https://skia.googlesource.com/skia/+/1763492c32d424634ed9e56eabded2b27d964747

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

ClusterFuzz has detected this issue as fixed in range 527343:527367.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  bad_int
  any_bad_ints
  do_anti_hairline
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=523469:523491
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=527343:527367

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

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.

ClusterFuzz testcase 6630813478420480 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.