Timeout in icu_uregex_open_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5709739965808640 Fuzzer: libFuzzer_icu_uregex_open_fuzzer Job Type: windows_libfuzzer_chrome_asan Platform Id: windows Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: icu_uregex_open_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5709739965808640 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 16
mnita@, just wondering do you have any inputs here? Thank you!
,
Dec 1
ClusterFuzz testcase 5709739965808640 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.
,
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 kkaluri@chromium.org
, Oct 15Labels: M-70 CF-NeedsTriage Test-Predator-Wrong