Automatically adding ccs based on suspected regression changelists:

https://chromium.googlesource.com/v8/v8/+/0afe2524c0e422806daa66d1fdf3a034a003640a ([wasm] Add fuzzing for Liftoff by clemensh@chromium.org)

https://chromium.googlesource.com/v8/v8/+/d1d48cce66441a12f6f9cbed33c0df388b99a40d ([wasm fuzzers] Add memory ops by eholk@chromium.org)

https://chromium.googlesource.com/v8/v8/+/0dbc81307ba5dd680735ce24bee6de46c4124344 ([wasm] Clean up and speed up compile fuzzer by clemensh@chromium.org)

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

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 514773:514780.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  interpreter != liftoff (NUMBER vs NUMBER); WasmCodeFuzzerHash=4bf807d2 in wasm-f
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=514357:514376
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=514773:514780

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

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.