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://chromium.googlesource.com/chromium/src/+/b185b42ecd9ef640053a8c3a0e044e6e1df069f1 (Remove no_size_t_to_int_warning in //url).

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.

Similar to https://bugs.chromium.org/p/chromium/issues/detail?id=778929.

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

commit e584ee73e7aea646b6b34d731ba68e96b34d678d
Author: Raul Tambre <raul@tambre.ee>
Date: Tue Jan 15 07:07:55 2019

Initialize ICU for gpu_fuzzer

Bug:  920618 
Change-Id: Ibd676ec100e6266a6203272342da3c8a8a6b7459
Reviewed-on: https://chromium-review.googlesource.com/c/1407697
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Raul Tambre <raul@tambre.ee>
Cr-Commit-Position: refs/heads/master@{#622763}
[modify] https://crrev.com/e584ee73e7aea646b6b34d731ba68e96b34d678d/gpu/BUILD.gn
[modify] https://crrev.com/e584ee73e7aea646b6b34d731ba68e96b34d678d/gpu/command_buffer/tests/fuzzer_main.cc

ClusterFuzz has detected this issue as fixed in range 622762:622763.

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

Fuzzer: libFuzzer_gpu_fuzzer
Fuzz target binary: gpu_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  false. failed to open UTS46 data with error: U_FILE_ACCESS_ERROR. If you see thi
  url::IDNToASCII
  url::DoIDNHost
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=619775:619802
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=622762:622763

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 5738958310604800 is verified as fixed, so closing issue as verified.

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