V8 correctness failure in configs: x64,ignition_turbo_opt:x64,ignition_turbo_opt_eager |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6490715319435264 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition_turbo_opt:x64,ignition_turbo_opt_eager sources: 1b6 Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=46722:46723 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6490715319435264 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Feb 2 2018
,
Feb 24 2018
Removing v8-foozzie-failure label, because eager-lazy testing has been removed from correctness-fuzzer experiments.
,
Aug 31
ClusterFuzz has detected this issue as fixed in range 55519:55520. Detailed report: https://clusterfuzz.com/testcase?key=6490715319435264 Fuzzer: foozzie_js_mutation Job Type: v8_foozzie Platform Id: linux Crash Type: V8 correctness failure Crash Address: Crash State: configs: x64,ignition_turbo_opt:x64,ignition_turbo_opt_eager sources: 1b6 Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=46722:46723 Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=55519:55520 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6490715319435264 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.
,
Aug 31
ClusterFuzz testcase 6490715319435264 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
, Nov 23 2017Owner: gsat...@chromium.org
Status: Assigned (was: Untriaged)