Looks like the bugs are still there. They were just temporarily swallowed by the switch. This is maybe still  issue 680110 . PTAL

 Issue 681092  has been merged into this issue.

 Issue 681126  has been merged into this issue.

 Issue 681336  has been merged into this issue.

 Issue 681335  has been merged into this issue.

 Issue 681346  has been merged into this issue.

 Issue 681354  has been merged into this issue.

 Issue 681361  has been merged into this issue.

 Issue 681403  has been merged into this issue.

 Issue 681597  has been merged into this issue.

 Issue 681770  has been merged into this issue.

 Issue 681793  has been merged into this issue.

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

commit e9981e076acc92709a5a12361d5ab03a9bf5144a
Author: machenbach <machenbach@chromium.org>
Date: Tue Jan 17 12:25:15 2017

[foozzie] Add test suppressions

BUG= chromium:681088 , chromium:681236 
NOTRY=true
TBR=bradnelson@chromium.org, titzer@chromium.org

Review-Url: https://codereview.chromium.org/2632223002
Cr-Commit-Position: refs/heads/master@{#42402}

[modify] https://crrev.com/e9981e076acc92709a5a12361d5ab03a9bf5144a/tools/foozzie/v8_suppressions.py

ClusterFuzz testcase 5524134663815168 is verified as fixed, so closing issue.

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

Wrongly closed because it's suppressed now.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4595987667746816

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  suppression:  crbug.com/681088 
  
Sanitizer: address (ASAN)

Regressed: V8: r42401:42402

Minimized Testcase (0.07 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv95VAYRt0nWDPMoituKT2-SS-93Ri2VCUAPiuxAJ59K4r3q_O_OgZn7s6SJy54Ixs5J-3O6oNcDRlhAmUMSpmXsLwR67XmZ-aTdJmGoz4SsSaRYMDJ1n5Lov0upeWG-Q2B1ysC8y_YSGimbAwffRPbbLMeRJmCfz37o3dzUFMWbOB0Bjjv33IxeApWihAnOW7gQRDfHs6MmPxz-_J7rW48EoAkYDRduHbRc44RF4b9Wg6zGPHp9cBjM5PNvMUFsEhMNuNMr-7fAZhaiAEDfaBwNB5BQcyAnpGqM_z93793lX8i8JRFXbRXPBPn9Fdq4EHlPPLcm2awHL-dwM4x4BmCsc3TP334GhWV0_Cu_XgpI__05FnTU?testcase_id=4595987667746816
print("v8-foozzie source: /v8/test/mjsunit/wasm/asm-wasm-stack.js");


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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

commit c5caaf8921ac4a0c0a9ae16a1a0d1962866d2b90
Author: machenbach <machenbach@chromium.org>
Date: Wed Jan 18 09:37:43 2017

[foozzie] Add stronger failures suppression for  crbug.com/681088 

BUG= chromium:681088 
NOTRY=true
TBR=bradnelson@chromium.org

Review-Url: https://codereview.chromium.org/2637423002
Cr-Commit-Position: refs/heads/master@{#42441}

[modify] https://crrev.com/c5caaf8921ac4a0c0a9ae16a1a0d1962866d2b90/tools/foozzie/v8_suppressions.py

ClusterFuzz has detected this issue as fixed in range 42445:42446.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5402562393276416

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,fullcode:x64,ignition_staging
  sources: 18c
  
Sanitizer: address (ASAN)

Regressed: V8: 42334:42335
Fixed: V8: 42445:42446

Minimized Testcase (0.64 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95jiljyclTz0mehAfgdZbQYW-iqy_Nt1jcLIPmDUl8D-ViUq60Z58wVIQtkBSiPQVmy-lbO8imXoPbR2nQ3nYGV-oKsKPD2i1W_-HC3QUpIxG3K_bLfvkT7Q8dknCMFQZ-yzN2ac1vopP3e3meoIToeOCkarT-Gy2acqKMM79j8WYVokOPEVKdIQBjueebyJe2qWYvvY3fPLxKkZS71j7-k6i-nVeY4pLZjO-hDqIa_8k0IMqayTB65Io5Ft-sDWv5X4XPyJptosM_Pe2CXymD3HLCyLlbbOVZt6YW1LiMyMay6z05OSLH6sAhQc9BljJSZX-bAvDHGyBAnITiU3ngecmHSvJVftxMkV-7Ddh8Qsj1a8AQ?testcase_id=5402562393276416

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

As discussed, moving to machenbach@ for further triage.

Is this wontfix by now? Doesn't repro anymore with current comparison.

The original issue is actually pretty much the same as  issue 715505 .

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

commit 1dfcc4b6876d866e803b0a0af05bd27418443cbe
Author: Michael Achenbach <machenbach@chromium.org>
Date: Thu Apr 27 14:49:13 2017

[foozzie] Remove obsolete suppressions

Most of these suppressions were for the old asm-validator or for the old compiler pipeline. Some more are just optimistically removed.

Bug:  chromium:681088 ,  chromium:681241 , chromium:681806,  chromium:662840 
NOTRY=true

Change-Id: I4c6851a72d22070026eeaca90ad3394cfce10f90
Reviewed-on: https://chromium-review.googlesource.com/488641
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#44942}
[modify] https://crrev.com/1dfcc4b6876d866e803b0a0af05bd27418443cbe/tools/foozzie/v8_foozzie_test.py
[modify] https://crrev.com/1dfcc4b6876d866e803b0a0af05bd27418443cbe/tools/foozzie/v8_suppressions.py

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.