Timeout in gpu_angle_passthrough_fuzzer |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5772816365125632 Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: gpu_angle_passthrough_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=5772816365125632 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Aug 30
mmoroz@, just wondering this (https://chromium.googlesource.com/chromium/src/+/6d7b69ac40b01d87e8499cb8232631c69bd3269a) is a related change? Thank you!
,
Aug 31
My change enabled new instrumentation which is somewhat slower than the old one, but more efficient for fuzzing / finding more bugs.
,
Dec 1
ClusterFuzz testcase 5772816365125632 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. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kkaluri@chromium.org
, Aug 17Labels: M-70 CF-NeedsTriage Test-Predator-Wrong