Timeout in v8_multi_return_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5181298591924224 Fuzzer: libFuzzer_v8_multi_return_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_multi_return_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=533258:533361 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5181298591924224 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Feb 13 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Feb 13 2018
,
Feb 13 2018
ClusterFuzz has detected this issue as fixed in range 536026:536122. Detailed report: https://clusterfuzz.com/testcase?key=5181298591924224 Fuzzer: libFuzzer_v8_multi_return_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_multi_return_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=533258:533361 Fixed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=536026:536122 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5181298591924224 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Feb 13 2018
ClusterFuzz testcase 5181298591924224 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Feb 13 2018
ClusterFuzz testcase 5181298591924224 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
, Feb 13 2018