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/+/bb253d28f48b6a2895b13f8a49d78fcc1be79779 ([fuzzer] Handle more than 256 parameters of the same type).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

I still have to investigate. However, this fuzzer tests a feature which is off-by-default at the moment and therefore I reduce the priority.

ClusterFuzz has detected this issue as fixed in range 544721:544735.

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

Fuzzer: libFuzzer_v8_multi_return_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  expect == result in multi-return.cc
  multi-return.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=534395:534400
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=544721:544735

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

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

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