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.

I'm beginning to think we need to remove this assert and have it return an error code or something so we can stop this from firing.

ClusterFuzz has detected this issue as fixed in range 607369:607371.

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

Fuzzer: libFuzzer_spvtools_opt_performance_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=607369:607371

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

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

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