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:

Attempt to correct for invalid central dir offsets. #340 by nathan@solidstatenetworks.com - https://chromium.googlesource.com/external/github.com/nmoinvaz/minizip/+/aacf87304ed93449e7a8b31a60a759fb97dbc184

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Stacktrace:
../../third_party/minizip/src/mz_zip.c:1751:66: runtime error: signed integer overflow: -9223372036849205248 + -4294904064 cannot be represented in type 'long'
     #0 0x555f27fc7295 in mz_zip_entry_read_open third_party/minizip/src/mz_zip.c:1751:66
     #1 0x555f27ecfff6 in LLVMFuzzerTestOneInput third_party/minizip/minizip_uncompress_fuzzer.cc:48:16
    #2 0x555f27edc5d5 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, unsigned long) third_party/libFuzzer/src/FuzzerLoop.cpp:571:15
    #3 0x555f27ed30fc in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) third_party/libFuzzer/src/FuzzerDriver.cpp:280:6
    #4 0x555f27ed57bb in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) third_party/libFuzzer/src/FuzzerDriver.cpp:713:9
    #5 0x555f27ee22c2 in main third_party/libFuzzer/src/FuzzerMain.cpp:20:10

ClusterFuzz testcase 4882536347729920 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.

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

commit bdd979e4d2b8ed59fbabd1067739409fcb2e64eb
Author: Anand K. Mistry <amistry@chromium.org>
Date: Mon Dec 17 04:38:59 2018

Uprev minizip to 2.8.1

BUG=906333, 906354 , 906350 

Change-Id: I5c383697a8a168865263b79bc8c4e264380d5c66
Reviewed-on: https://chromium-review.googlesource.com/c/1373249
Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Anand Mistry <amistry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#617048}
[modify] https://crrev.com/bdd979e4d2b8ed59fbabd1067739409fcb2e64eb/DEPS
[modify] https://crrev.com/bdd979e4d2b8ed59fbabd1067739409fcb2e64eb/third_party/minizip/BUILD.gn
[modify] https://crrev.com/bdd979e4d2b8ed59fbabd1067739409fcb2e64eb/third_party/minizip/README.chromium
[modify] https://crrev.com/bdd979e4d2b8ed59fbabd1067739409fcb2e64eb/ui/file_manager/integration_tests/file_manager/zip_files.js

ClusterFuzz has detected this issue as fixed in range 617047:617048.

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

Fuzzer: libFuzzer_minizip_uncompress_fuzzer
Fuzz target binary: minizip_uncompress_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  mz_zip_entry_read_open
  minizip_uncompress_fuzzer.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=605984:605985
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=617047:617048

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

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

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