New issue
Advanced search Search tips

Issue 882117 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 21
Cc:
pwang@chromium.org
zachr@google.com
manojgupta@chromium.org
marcheu@google.com
davidriley@google.com
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in chromeos_virgl_fuzzer

Project Member Reported by ClusterFuzz, Sep 8 
Detailed report: https://clusterfuzz.com/testcase?key=6454638419902464

Fuzzer: libFuzzer_chromeos_virgl_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  chromeos_virgl_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=2801419:2801745

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6454638419902464

Issue filed automatically.

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
Project Member

Comment 1 by ClusterFuzz, Sep 8

Cc: davidriley@google.com marcheu@google.com zachr@google.com
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.
Project Member

Comment 2 by ClusterFuzz, Sep 12

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6454638419902464 appears to be flaky, updating reproducibility label.

Comment 3 by infe...@chromium.org, Sep 14

Labels: -Unreproducible Reproducible

Comment 4 by marc...@chromium.org, Sep 20

Cc: pwang@chromium.org
Project Member

Comment 5 by ClusterFuzz, Sep 21

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 6454638419902464 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
►

Sign in to add a comment