Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/9f57237995f7921b4dcd8855f1f6fe98874218d2 (Switch to new ffmpeg decoder APIs.).

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.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e40dd6362f9b9f3aa4fee56c7a7fe56e4b49b173

commit e40dd6362f9b9f3aa4fee56c7a7fe56e4b49b173
Author: Dale Curtis <dalecurtis@chromium.org>
Date: Sat May 05 00:59:56 2018

Always install error handler when waiting for PipelineIntegrationTests.

Some of the fuzzing tests invoke errors at weird times, in the case
of the linked bug: during seek, preventing the pipeline from reaching
have enough again and thus hanging forever.

There doesn't seem to be any reason not to include an error handler
during all waits done by PipelineIntegrationTests, hanging should
not be the behavior used by tests to indicate failure.

BUG= 834559 
TEST=fuzzer test exits instead of hanging

Change-Id: Ieccf1b4647ab8aa0f3e5ad22a3174c2f251468ec
Reviewed-on: https://chromium-review.googlesource.com/1045562
Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556281}
[modify] https://crrev.com/e40dd6362f9b9f3aa4fee56c7a7fe56e4b49b173/media/test/pipeline_integration_fuzzertest.cc
[modify] https://crrev.com/e40dd6362f9b9f3aa4fee56c7a7fe56e4b49b173/media/test/pipeline_integration_test_base.cc
[modify] https://crrev.com/e40dd6362f9b9f3aa4fee56c7a7fe56e4b49b173/media/test/pipeline_integration_test_base.h

ClusterFuzz has detected this issue as fixed in range 556276:556281.

Detailed report: https://clusterfuzz.com/testcase?key=6636415996395520

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=513664:513691
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=556276:556281

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

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.

ClusterFuzz testcase 6636415996395520 is verified as fixed, so closing issue as verified.

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