Timeout in sfntly_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6495956389068800 Fuzzer: libFuzzer_sfntly_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: sfntly_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=459635:459640 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6495956389068800 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Mar 1 2018
,
Apr 12 2018
,
Nov 10
,
Dec 1
ClusterFuzz testcase 6495956389068800 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 18
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by brajkumar@chromium.org
, Feb 28 2018Components: Internals>Skia>PDF
Labels: M-65 Test-Predator-Wrong
Owner: thestig@chromium.org
Status: Assigned (was: Untriaged)