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.

To dneto@ for triage.

denot@ or cwallez@, did these fuzzers get added for WebGPU? Who is the correct person to triage going forward?

ClusterFuzz has detected this issue as fixed in range 608864:608878.

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

Fuzzer: libFuzzer_spvtools_opt_size_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  base_inst->IsValidBasePointer() && "We cannot have a base pointer come from this
  spvtools::opt::Instruction::GetBaseAddress
  spvtools::opt::MemPass::GetPtr
  
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=608864:608878

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

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

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

This fuzzer is not part of Dawn but SPIRV-Tools itself and issues should be assigned to dsinclair for triage.

This was probably fixed by something Steven added while fixing up fuzzer issues last week.