Timeout in renderer_fuzzer |
|||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4570766197391360 Fuzzer: libFuzzer_renderer_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: renderer_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=408266:408346 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4570766197391360 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
May 15 2018
Predator could not provide any possible suspects. From the above CL observing some changes related to 'renderer_fuzzer' , hence suspecting the same Suspect CL: https://chromium.googlesource.com/chromium/src/+/a5eaabc15d7aa4f4ca4bba17b669435da5c9dab8 aizatsky@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Thanks!
,
May 16 2018
,
Oct 10
,
Dec 1
ClusterFuzz testcase 4570766197391360 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 6
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ClusterFuzz
, May 12 2018Labels: ClusterFuzz-Auto-CC