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

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

Automatically adding ccs based on suspected regression changelists:

remove scaling from pathops by caryclark@skia.org - https://skia.googlesource.com/skia/+/5de5233463ddfae51965a116177b2ce62c883765

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

The following revision refers to this bug:
  https://skia.googlesource.com/skia/+/5369e1422fe83e5b467acc5a1f9f008da517062c

commit 5369e1422fe83e5b467acc5a1f9f008da517062c
Author: Cary Clark <caryclark@skia.org>
Date: Mon Nov 19 20:34:01 2018

fix pathops fuzzer timeout

add safety net if it gets
stuck in a loop. Also fix
skia fuzzer latest.

R=kjlubick@google.com

Bug:  906360 
Change-Id: Iabb608f615838b6b7ec9e001ec5664e84566c274
Reviewed-on: https://skia-review.googlesource.com/c/171902
Commit-Queue: Cary Clark <caryclark@skia.org>
Commit-Queue: Kevin Lubick <kjlubick@google.com>
Auto-Submit: Cary Clark <caryclark@skia.org>
Reviewed-by: Kevin Lubick <kjlubick@google.com>

[modify] https://crrev.com/5369e1422fe83e5b467acc5a1f9f008da517062c/src/pathops/SkOpSegment.cpp
[modify] https://crrev.com/5369e1422fe83e5b467acc5a1f9f008da517062c/src/pathops/SkOpCoincidence.cpp

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5ef141e9b0f04a43469b5f24ebd47b21325b1a92

commit 5ef141e9b0f04a43469b5f24ebd47b21325b1a92
Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Date: Mon Nov 19 23:08:38 2018

Roll src/third_party/skia 4065d45d2de1..a63cf8e80aa5 (5 commits)

https://skia.googlesource.com/skia.git/+log/4065d45d2de1..a63cf8e80aa5


git log 4065d45d2de1..a63cf8e80aa5 --date=short --no-merges --format='%ad %ae %s'
2018-11-19 rmistry@google.com Revert "Temporarily remove Android compile bot from CQ"
2018-11-19 csmartdalton@google.com Fix handling of dynamic state in GrAAFillRRectOp
2018-11-19 caryclark@skia.org fix pathops fuzzer timeout
2018-11-19 csmartdalton@google.com Add a dedicated Op for analytic round rects
2018-11-19 caryclark@skia.org font doc


Created with:
  gclient setdep -r src/third_party/skia@a63cf8e80aa5

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel

BUG= chromium:906360 ,chromium:860021
TBR=csmartdalton@chromium.org

Change-Id: I3c1331d3b9337150cdbf5a8e4d01a679231b2a6d
Reviewed-on: https://chromium-review.googlesource.com/c/1343180
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#609488}
[modify] https://crrev.com/5ef141e9b0f04a43469b5f24ebd47b21325b1a92/DEPS

ClusterFuzz has detected this issue as fixed in range 609487:609489.

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

Fuzzer: libFuzzer_skia_pathop_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  skia_pathop_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=588097:588106
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=609487:609489

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

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

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