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.

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

commit 7b9ba30b36ca9361d09404883e086e4fc4f30791
Author: Wez <wez@chromium.org>
Date: Mon Jan 14 17:40:38 2019

Fix BlinkFuzzerTestSuppport to initialize TestTimeouts.

Bug:  921137 
Change-Id: I8144574710cd02c42750be347838b9305b31bd72
Reviewed-on: https://chromium-review.googlesource.com/c/1407256
Commit-Queue: Wez <wez@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#622501}
[modify] https://crrev.com/7b9ba30b36ca9361d09404883e086e4fc4f30791/third_party/blink/renderer/platform/testing/blink_fuzzer_test_support.cc

ClusterFuzz has detected this issue as fixed in range 622498:622501.

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

Fuzzer: libFuzzer_text_resource_decoder_fuzzer
Fuzz target binary: text_resource_decoder_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=622498:622501

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

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 6328175545810944 is verified as fixed, so closing issue as verified.

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