Wasm is chatty |
||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5346139261108224 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie_ignition_staging Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,fullcode:x64,ignition_staging sources: cd626806 Minimized Testcase (2.62 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96s5ReimyVR_nJ-xe_30PyU2hRBqj0pzux4dyHuELxEXLuaEM1nO-CKpThP1W2B8hxOziPCFG5resr1xGQ4WYF_bGlTHO3Fo15g21F9JBfWeNlQDr7wiLp5pz5hFyC-4oTgSge44d0sQlQzLhxv_m2zp4JhmQ?testcase_id=5346139261108224 Issue manually filed by: machenbach See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Dec 26 2016
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/4cdee4fd85f6c3435f6309b22e79143ec3ac0283 commit 4cdee4fd85f6c3435f6309b22e79143ec3ac0283 Author: machenbach <machenbach@chromium.org> Date: Mon Dec 26 17:14:36 2016 [foozzie] Ignore some wasm console output BUG= chromium:677032 NOTRY=true TBR=titzer@chromium.org Review-Url: https://codereview.chromium.org/2607473002 Cr-Commit-Position: refs/heads/master@{#41955} [modify] https://crrev.com/4cdee4fd85f6c3435f6309b22e79143ec3ac0283/tools/foozzie/v8_suppressions.py
,
Dec 26 2016
ClusterFuzz has detected this issue as fixed in the latest custom build. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5346139261108224 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie_ignition_staging Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,fullcode:x64,ignition_staging sources: cd626806 Minimized Testcase (2.62 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96s5ReimyVR_nJ-xe_30PyU2hRBqj0pzux4dyHuELxEXLuaEM1nO-CKpThP1W2B8hxOziPCFG5resr1xGQ4WYF_bGlTHO3Fo15g21F9JBfWeNlQDr7wiLp5pz5hFyC-4oTgSge44d0sQlQzLhxv_m2zp4JhmQ?testcase_id=5346139261108224 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.
,
Dec 26 2016
ClusterFuzz testcase 5346139261108224 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Apr 11 2017
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/51a1b0b0d3acd1c7858b569dd1762c3216edbef7 commit 51a1b0b0d3acd1c7858b569dd1762c3216edbef7 Author: Michael Achenbach <machenbach@chromium.org> Date: Tue Apr 11 12:36:53 2017 [foozzie] Remove obsolete suppressions Bug: chromium:677032 NOTRY=true Change-Id: I820e9c89677f4028107719547c372f91e5feb271 Reviewed-on: https://chromium-review.googlesource.com/474805 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#44567} [modify] https://crrev.com/51a1b0b0d3acd1c7858b569dd1762c3216edbef7/tools/foozzie/v8_suppressions.py |
||
►
Sign in to add a comment |
||
Comment 1 by machenb...@chromium.org
, Dec 26 2016Labels: -Stability-Crash v8-foozzie-failure
Summary: Wasm is chatty (was: V8 correctness failure in configs: x64,fullcode:x64,ignition_staging)