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 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:

SPV_EXT_physical_storage_buffer (#2267) by jbolz@nvidia.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/5eab6df648eace6eab69c44ccd17bd0f5e57406d

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

An array type is referencing itself:

%_arr_23_int_267911167 = OpTypeArray %_arr_23_int_267911167 %int_267911167

Fixed with https://github.com/KhronosGroup/SPIRV-Tools/pull/2307.

ClusterFuzz has detected this issue as fixed in range 624608:624628.

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

Fuzzer: libFuzzer_spvtools_opt_performance_fuzzer
Fuzz target binary: spvtools_opt_performance_fuzzer
Job Type: chromeos_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000020
Crash State:
  spvtools::opt::analysis::Type::GetHashWords
  spvtools::opt::analysis::Array::GetExtraHashWords
  spvtools::opt::analysis::Type::GetHashWords
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=chromeos_libfuzzer_chrome_asan&range=620481:620482
Fixed: https://clusterfuzz.com/revisions?job=chromeos_libfuzzer_chrome_asan&range=624608:624628

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

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

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