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:

Move cfg opcode validation to another file. by alanbaker@google.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/6cd4441c878699d6f59b0ba73cbbdc80ae9ec28f

Fixing heap overflow in validation. by alanbaker@google.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/397e02442e63781f66c70978fffab7551fdadf3f

Split function opcode validation into new files. by alanbaker@google.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/e7fdcdba75eda1f5a70d689cf50628389efa3ed0

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

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

ClusterFuzz has detected this issue as fixed in range 601563:601570.

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

Fuzzer: libFuzzer_spvtools_val_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x00000000003a
Crash State:
  spvtools::val::Instruction::opcode
  spvtools::val::ValidationState_t::IsIntScalarType
  spvtools::val::ValidateVectorExtractDynamic
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=583090:583112
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=601563:601570

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

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

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