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 adding ccs based on OWNERS file / target commit history.

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/d9e4cb77324a3d4e0dfd6b599ce34e1224fdedb6 (Apply a default timeout to RunLoop::Run() calls on test main threads.).

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.

Posted a CL to fix this at https://chromium-review.googlesource.com/c/chromium/src/+/1403186 and TBR'd to xhwang, to un-break the fuzzer bots ASAP.

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

commit a72257bad57d95dbc42dc00c8ebc588e2fd8586f
Author: Wez <wez@chromium.org>
Date: Wed Jan 09 18:58:29 2019

Initialize base::TestTimeouts in media_pipeline_integration_fuzzer.

The PipelineIntegrationTestBase uses ScopedTaskEnvironment internally,
which now requires that TestTimeouts were Initialize()d for the process.

TBR=xhwang

Bug:  920111 ,  918724 
Change-Id: Idbf0197eb160fe8af2195f50e2e3da58f25a17a5
Reviewed-on: https://chromium-review.googlesource.com/c/1403186
Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#621247}
[modify] https://crrev.com/a72257bad57d95dbc42dc00c8ebc588e2fd8586f/media/test/BUILD.gn
[modify] https://crrev.com/a72257bad57d95dbc42dc00c8ebc588e2fd8586f/media/test/pipeline_integration_fuzzertest.cc

 Issue 920364  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 621245:621247.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Fuzz target binary: media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  initialized_ in test_timeouts.h
  TestTimeouts::action_max_timeout
  base::test::ScopedTaskEnvironment::ScopedTaskEnvironment
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=621021:621022
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=621245:621247

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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

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