Timeout in v8_fully_instrumented_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5688565838905344 Fuzzer: libFuzzer_v8_fully_instrumented_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: v8_fully_instrumented_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=583285:583294 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5688565838905344 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 5
,
Nov 15
to CF sheriff for retriage.
,
Dec 1
ClusterFuzz testcase 5688565838905344 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 9
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ClusterFuzz
, Nov 4Labels: ClusterFuzz-Auto-CC