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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/41bd98e703d9037d8522ff5d5613314c55a48e6c ([wasm fuzzer] generate grow_memory instructions).

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

These are probably all dupes of the original one. Clemens, can you confirm? I'm guessing the fix is in but it may take time to get to all the fuzzers, right?

ClusterFuzz has detected this issue as fixed in range 515947:515970.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  interpreter != liftoff (fffffed7 vs ff3e9ed3); WasmCodeFuzzerHash=4ce061fa in wa
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  _start
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514774:514785
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=515947:515970

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

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.