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/+/f0b761f116f663dbe344d70a785219af49f537d5 (Implement timeline fences in Dawn).

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 has detected this issue as fixed in range 613934:613941.

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

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

Crash Type: Direct-leak
Crash Address: 
Crash State:
  dawn_native::DeviceBase::CreateFenceInternal
  dawn_native::DeviceBase::CreateFence
  dawn_wire::server::Server::HandleDeviceCreateFence
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613294:613296
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=613934:613941

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

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

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