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

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

With reference to the  Issue 912628 , assigning it to yguyon@

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

commit 2772b746b4f460a3d67a694430b93ca8570b804c
Author: Yannis Guyon <yguyon@google.com>
Date: Mon Dec 17 19:19:49 2018

third_party/libwebp/fuzzing: Restrict colorspace

In target libwebp_simple_api_fuzzer, restrict WebPDecode*() and
WebPDecode*Into() to RGBA, BGRA and YUV, the only supported modes
when WEBP_REDUCE_CSP is defined, which is the case in chromium.

BUG= chromium:915156 

Change-Id: I1553d75cff2d26ec29323f515f3fd7700af15277
Reviewed-on: https://chromium-review.googlesource.com/c/1379892
Reviewed-by: James Zern <jzern@google.com>
Commit-Queue: Yannis Guyon <yguyon@google.com>
Cr-Commit-Position: refs/heads/master@{#617181}
[modify] https://crrev.com/2772b746b4f460a3d67a694430b93ca8570b804c/third_party/libwebp/fuzzing/fuzz_simple_api.cc

ClusterFuzz has detected this issue as fixed in range 617179:617181.

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

Fuzzer: libFuzzer_libwebp_simple_api_fuzzer
Fuzz target binary: libwebp_simple_api_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  0
  EmptyUpsampleFunc
  EmitFancyRGB
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=614208:614220
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=617179:617181

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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

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