Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/4e22b601224b1ddc3eb60ab38d9d1d89e81135e5 (Add validation for OpArrayLength. (#2117)).

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 4840303728787456 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.

https://github.com/KhronosGroup/SPIRV-Tools/pull/2155

Fixed by https://github.com/KhronosGroup/SPIRV-Tools/pull/2142.

ClusterFuzz has detected this issue as fixed in range 613214:613216.

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

Fuzzer: libFuzzer_spvtools_val_fuzzer
Fuzz target binary: spvtools_val_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x00000000003a
Crash State:
  spvtools::val::MemoryPass
  spvtools::val::ValidateBinaryUsingContextAndValidationState
  spvValidateBinary
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=611026:611388
Fixed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=613214:613216

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

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

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

The documentation for reproducing bugs on Windows was moved to: https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md