New issue
Advanced search Search tips

Issue 879223 link

Starred by 1 user
Status: Assigned
Owner:
wolenetz@chromium.org
Cc:
pnangunoori@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in mediasource_WEBM_VP9_pipeline_integration_fuzzer

Project Member Reported by ClusterFuzz, Aug 30 
Detailed report: https://clusterfuzz.com/testcase?key=5834116839505920

Fuzzer: libFuzzer_mediasource_WEBM_VP9_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  mediasource_WEBM_VP9_pipeline_integration_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=583292:583305

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

Comment 1 by pnangunoori@chromium.org, Aug 31

Cc: pnangunoori@chromium.org
Labels: M-70 Test-Predator-Wrong
Owner: wolenetz@chromium.org
Status: Assigned (was: Untriaged)
As per the  Issue 825784  owner, assigning this issue to wolenetz@.
@wolenetz-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thanks.
Project Member

Comment 2 by ClusterFuzz, Dec 1

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

Comment 3 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
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.

Comment 4 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
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