V8 correctness failure in configs: x64,ignition:x64,ignition_turbo |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5623969167441920 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition:x64,ignition_turbo sources: 24d Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48039:48040 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5623969167441920 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 18 2017
Lower prio since it seems to be an error message problem only. Do we need to suppress it?
,
Sep 20 2017
ClusterFuzz has detected this issue as fixed in range 48082:48083. Detailed report: https://clusterfuzz.com/testcase?key=5623969167441920 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition:x64,ignition_turbo sources: 24d Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48039:48040 Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=48082:48083 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5623969167441920 See https://github.com/google/clusterfuzz-tools for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Sep 20 2017
The CL was reverted but I'll try again, will address this issue too.
,
Sep 20 2017
ClusterFuzz testcase 5623969167441920 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by machenb...@chromium.org
, Sep 18 2017Owner: mvstan...@chromium.org
Status: Assigned (was: Untriaged)