Timeout in hit_test_query_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5953362777079808 Fuzzer: libFuzzer_hit_test_query_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: hit_test_query_fuzzer Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=548211:548216 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5953362777079808 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Apr 22 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Apr 22 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/9d4d1fef05cca5398d6ae8dfbd6c5f552bff6389 (viz: Fix the fuzzer for hit-test query.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Nov 8
ClusterFuzz has detected this issue as fixed in range 606133:606148. Detailed report: https://clusterfuzz.com/testcase?key=5953362777079808 Fuzzer: libFuzzer_hit_test_query_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: hit_test_query_fuzzer Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=548211:548216 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=606133:606148 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5953362777079808 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Nov 8
ClusterFuzz testcase 5953362777079808 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Apr 22 2018