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 adding ccs based on suspected regression changelists:

Version 6.6.110 by v8-autoroll@chromium.org - https://chromium.googlesource.com/v8/v8/+/3c62a1eca6618b31822ec3d19cc2499e74e0a2de

[wasm] [fuzzer] Also generate br_if by clemensh@chromium.org - https://chromium.googlesource.com/v8/v8/+/3e43bbb544a7f425ee9cf8b2c1e4e0fd7825b3db

[wasm] Move ScheduledErrorThrower into wasm-js.cc file. by mstarzinger@chromium.org - https://chromium.googlesource.com/v8/v8/+/5cc8a2c50b3a2ca87fb0eb796bebb7b335e71011

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Most likely mine. I'll take a look.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/e210ee55f578ab9ccc899d5b67f4de78dd4d0f58

commit e210ee55f578ab9ccc899d5b67f4de78dd4d0f58
Author: Michael Starzinger <mstarzinger@chromium.org>
Date: Wed Jan 31 13:31:36 2018

[wasm] Fix handling of pending exceptions in fuzzer.

R=clemensh@chromium.org
BUG= chromium:807508 

Change-Id: I0b90b93a796c67f557e392cf6123a48cd0942bd7
Reviewed-on: https://chromium-review.googlesource.com/895303
Reviewed-by: Clemens Hammacher <clemensh@chromium.org>
Commit-Queue: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#50993}
[modify] https://crrev.com/e210ee55f578ab9ccc899d5b67f4de78dd4d0f58/test/fuzzer/wasm-fuzzer-common.cc

ClusterFuzz has detected this issue as fixed in range 533407:533416.

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

Fuzzer: libFuzzer_v8_wasm_async_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  !__isolate__->has_pending_exception() in builtins-api.cc
  v8::internal::MaybeHandle<v8::internal::Object> v8::internal::HandleApiCallHelpe
  v8::internal::Builtin_Impl_HandleApiCall
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=532879:532883
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=533407:533416

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

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot