V8 correctness failure in configs: x64,ignition:x64,ignition_turbo |
||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5794986938597376 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: f3a Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=50260:50261 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5794986938597376 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 23 2017
ClusterFuzz has detected this issue as fixed in range 50297:50298. Detailed report: https://clusterfuzz.com/testcase?key=5794986938597376 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: f3a Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=50260:50261 Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=50297:50298 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5794986938597376 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.
,
Dec 23 2017
ClusterFuzz testcase 5794986938597376 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 ClusterFuzz
, Dec 22 2017Owner: danno@chromium.org
Status: Assigned (was: Untriaged)