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:

Support scaled color emojis for SDF fallback by jvanverth@google.com - https://skia.googlesource.com/skia/+/c65b65dd816b7a9fbd148f577f0271cd555c4df6

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

This appears to be something real, but unrelated to my change. I'm not sure what it should do if the rect is not sorted. Sort the rect? Fail? 

The following revision refers to this bug:
  https://skia.googlesource.com/skia/+/5d32b83102a4477632f0bd360b3584a144329186

commit 5d32b83102a4477632f0bd360b3584a144329186
Author: Jim Van Verth <jvanverth@google.com>
Date: Wed Feb 21 16:43:02 2018

Add isFinite() bounds check for drawPoints

Bug:  811095 
Change-Id: I09a55622a19ebfc9430d7676eb8764c074f1bcb7
Reviewed-on: https://skia-review.googlesource.com/109022
Reviewed-by: Herb Derby <herb@google.com>
Commit-Queue: Jim Van Verth <jvanverth@google.com>

[modify] https://crrev.com/5d32b83102a4477632f0bd360b3584a144329186/src/core/SkCanvas.cpp

ClusterFuzz has detected this issue as fixed in range 538208:538224.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900005e75
Crash State:
  sk_abort_no_print
  SkPaint::computeFastBounds
  SkPaint::computeFastBounds
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=529788:529845
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=538208:538224

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

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 6724021115420672 is verified as fixed, so closing issue as verified.

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