Timeout in xml_parser_fuzzer |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6319756296323072 Fuzzer: libFuzzer_xml_parser_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: xml_parser_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=583292:583305 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6319756296323072 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 21
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!
,
Dec 1
ClusterFuzz testcase 6319756296323072 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 4
Looping libxml OWNERS: https://cs.chromium.org/chromium/src/third_party/libxml/OWNERS for further inputs here.
,
Dec 11
,
Dec 13
,
Jan 19
(4 days ago)
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Nov 18Labels: ClusterFuzz-Auto-CC