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

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

ClusterFuzz has detected this issue as fixed in range 613540:613541.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Fuzz target binary: v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  interpreter: exception; compiled: no exception in wasm-fuzzer-common.cc
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  wasm-compile.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=613045:613050
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=613540:613541

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

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

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