V8 correctness failure in configs: x64,ignition:x64,ignition_turbo_opt |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6645990466781184 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_opt sources: 7d9 Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=49684:49685 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6645990466781184 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Jan 10 2018
ClusterFuzz has detected this issue as fixed in range 50464:50465. Detailed report: https://clusterfuzz.com/testcase?key=6645990466781184 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_opt sources: 7d9 Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=49684:49685 Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=50464:50465 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6645990466781184 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.
,
Jan 10 2018
The fixed analysis makes no sense. This should be manually checked. Maybe the issue is a bit flaky.
,
Jan 10 2018
ClusterFuzz testcase 6645990466781184 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jan 10 2018
Re-assigning for manual verification.
,
Nov 15
This doesn't reproduce anymore. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Dec 2 2017Owner: u...@chromium.org
Status: Assigned (was: Untriaged)