Timeout in safe_browsing_hfs_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5636237288013824 Fuzzer: libFuzzer_safe_browsing_hfs_fuzzer Job Type: mac_libfuzzer_chrome_asan Platform Id: mac Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: safe_browsing_hfs_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_libfuzzer_chrome_asan&range=509376:509426 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5636237288013824 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 14
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/902112f50d2142fe611aac017954cfd5024023e6 (Add a new safe_browsing DMG fuzzer for the HFS+ layer.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Dec 1
ClusterFuzz testcase 5636237288013824 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 14Labels: ClusterFuzz-Auto-CC