CHECK failure: result != UPDATE_OK in appcache_update_job.cc |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5971600323248128 Fuzzer: libFuzzer_appcache_fuzzer Fuzz target binary: appcache_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: result != UPDATE_OK in appcache_update_job.cc content::AppCacheUpdateJob::HandleCacheFailure content::AppCacheUpdateJob::HandleManifestRefetchCompleted Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=623041:623074 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5971600323248128 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Jan 19
(3 days ago)
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Jan 19
(3 days ago)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/1aa9b656abfeee72404eaa29be04868bf897515c ([AppCache] Initialize TestTimeouts in appcache_fuzzer.). 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. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Jan 19 (3 days ago)Labels: Test-Predator-Auto-Components