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/+/62b3004439cab5e246c66803c5841c35b2df9c90

commit 62b3004439cab5e246c66803c5841c35b2df9c90
Author: Cary Clark <caryclark@skia.org>
Date: Tue Oct 23 14:33:15 2018

fix Simplify pathop fuzz

Simplify was out of sync with Op, and needed
to return failure when contour could not be
followed.

Also fix timeout where coincident detection
got stuck.

R=kjlubick@google.com

Bug:898114
Change-Id: Ia9076b9fd48e093bcc40ef21809c8eabe4cb9367
Reviewed-on: https://skia-review.googlesource.com/c/164601
Commit-Queue: Cary Clark <caryclark@google.com>
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/62b3004439cab5e246c66803c5841c35b2df9c90/src/pathops/SkOpSegment.cpp
[modify] https://crrev.com/62b3004439cab5e246c66803c5841c35b2df9c90/src/pathops/SkPathOpsSimplify.cpp

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

commit 461889ba6f1f4ebde65734a9c21a151f4142301f
Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Date: Tue Oct 23 16:39:21 2018

Roll src/third_party/skia 00766bf8dda1..62b3004439ca (4 commits)

https://skia.googlesource.com/skia.git/+log/00766bf8dda1..62b3004439ca


git log 00766bf8dda1..62b3004439ca --date=short --no-merges --format='%ad %ae %s'
2018-10-23 caryclark@skia.org fix Simplify pathop fuzz
2018-10-23 kjlubick@google.com Have FuzzPathop make a new path every time
2018-10-23 brianosman@google.com Remove colorType and colorSpace from bitmap cache key, and IWYU
2018-10-23 kjlubick@google.com Add Legacy fuzz reproducer


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

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:898114 ,chromium:897455
TBR=brianosman@chromium.org

Change-Id: Ib7d71aa1546b8cb74a43e4dad75c7df9897d2a71
Reviewed-on: https://chromium-review.googlesource.com/c/1296790
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@{#601984}
[modify] https://crrev.com/461889ba6f1f4ebde65734a9c21a151f4142301f/DEPS

ClusterFuzz has detected this issue as fixed in range 601980:601984.

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

Fuzzer: libFuzzer_skia_pathop_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  skia_pathop_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=588102:588113
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=601980:601984

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

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

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