Timeout in sqlite3_ossfuzz_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5876033016037376 Fuzzer: libFuzzer_sqlite3_ossfuzz_fuzzer Job Type: windows_libfuzzer_chrome_asan Platform Id: windows Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: sqlite3_ossfuzz_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=608966:609001 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5876033016037376 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing_on_windows.md for more information.
,
Nov 19
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!
,
Nov 19
mpdenton@, just wondering if this change (https://chromium.googlesource.com/chromium/src/+/5cb3a6cd8648c1585a8bd47c8333c5e406476527) is related? Thank you!
,
Nov 19
Well, that change essentially landed the fuzzer. I'm not sure what to do about fuzzer timeouts. It seems like they are to be expected for pathologically bad inputs.
,
Dec 1
ClusterFuzz testcase 5876033016037376 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 5
,
Dec 6
,
Dec 14
The documentation for reproducing on Windows has been moved to https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, Nov 18