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 556128:556143.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Ill
Crash Address: 0x000000ff770e
Crash State:
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  wasm-compile.cc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=553288:553308
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=556128:556143

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

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

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