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.

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

ClusterFuzz has detected this issue as fixed in range 619720:619724.

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

Fuzzer: libFuzzer_spvtools_opt_legalization_fuzzer
Fuzz target binary: spvtools_opt_legalization_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  index < operands_.size() && "operand index out of bound"
  spvtools::opt::Instruction::GetOperand
  spvtools::opt::Instruction::GetSingleWordOperand
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=579911:580305
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=619720:619724

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

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

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