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:

Initialize GLContextAttribs for the non-stub GPU fuzzer context. by geofflang@chromium.org - https://chromium.googlesource.com/chromium/src/+/ab52f8be0a3d00e28d88d33e2f0bcfc7a6fd0c3b

Moving GPUInfo's driver info to per GPU. by zmo@chromium.org - https://chromium.googlesource.com/chromium/src/+/fbea81d0d1b3c2ae22c5b1e2ee2d4a08c8f527f5

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://chromium.googlesource.com/angle/angle/+/21edf3db5e3330a4d65b102d9a917e7ce55dc230

commit 21edf3db5e3330a4d65b102d9a917e7ce55dc230
Author: Yuly Novikov <ynovikov@chromium.org>
Date: Tue Jul 24 21:28:13 2018

Fix stencil mask check in Framebuffer::partialClearNeedsInit

Bug:  850060 

Change-Id: I9672e6c93e92941e61763d77180bef1548f5fbde
Reviewed-on: https://chromium-review.googlesource.com/1148897
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>

[modify] https://crrev.com/21edf3db5e3330a4d65b102d9a917e7ce55dc230/src/libANGLE/Framebuffer.cpp

ClusterFuzz has detected this issue as fixed in range 577725:577726.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  depthStencil.stencilBackMask == depthStencil.stencilMask
  gl::Framebuffer::partialClearNeedsInit
  gl::Framebuffer::ensureClearAttachmentsInitialized
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=563689:563704
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=577725:577726

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

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

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