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

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

These keep coming in, should we move the assert into an ifndef NDEBUG statement or something so it will keep clusterfuzz happy?

ClusterFuzz has detected this issue as fixed in range 606051:606061.

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

Fuzzer: libFuzzer_spvtools_opt_size_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  0 && "Unhandled SPIR-V target environment"
  spvTargetEnvDescription
  spvtools::val::VersionCheck
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=581969:581979
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=606051:606061

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

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

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