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

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

Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/45ee4c88c43f2cd986a4af84ac4a8361a222b185 (Add a fuzzer for the wire server and Dawn frontend).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

ClusterFuzz testcase 5913501589307392 appears to be flaky, updating reproducibility label.

Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

ClusterFuzz has detected this issue as fixed in range 613933:613935.

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

Fuzzer: libFuzzer_dawn_wire_server_and_frontend_fuzzer
Fuzz target binary: dawn_wire_server_and_frontend_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Direct-leak
Crash Address: 
Crash State:
  dawn_native::null::Device::CreateDepthStencilState
  dawn_native::DepthStencilStateBuilder::GetResultImpl
  dawn_native::Builder<dawn_native::DepthStencilStateBase>::GetResult
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=607416:607428
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=613933:613935

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

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

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