Timeout in safe_browsing_dmg_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5730318294974464 Fuzzer: libFuzzer_safe_browsing_dmg_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: safe_browsing_dmg_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=429907:429934 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5730318294974464 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 11
Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue. Thanks!
,
Oct 11
rsesek@, I know this is pretty old change, however can you please see if this (https://chromium.googlesource.com/chromium/src/+/39ad5ff8e03689a22f387699b595952a7dc93fda) is related? Thank you!
,
Dec 1
ClusterFuzz testcase 5730318294974464 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Oct 10Labels: ClusterFuzz-Auto-CC