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/+/f4683a37ef679c4b1ea669855567a7938724389a (Add a different config param to control connection migration v2 on).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

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

commit 56e44b20420dab5682cc48920ed42ce487e9e04f
Author: Zhongyi Shi <zhongyi@chromium.org>
Date: Sat Dec 02 00:06:33 2017

Fix QuicStreamFactoryFuzzer initialization with connection migration v2

Bug:  790997 ,  774622 
Change-Id: I4b254e962d8aed0c10130b891d250980f412b088
Reviewed-on: https://chromium-review.googlesource.com/803620
Reviewed-by: Buck Krasic <ckrasic@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521135}
[modify] https://crrev.com/56e44b20420dab5682cc48920ed42ce487e9e04f/net/quic/chromium/quic_stream_factory_fuzzer.cc

ClusterFuzz has detected this issue as fixed in range 521121:521163.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !(close_sessions_on_ip_change && migrate_sessions_on_network_change_v2) in quic_
  net::QuicStreamFactory::QuicStreamFactory
  quic_stream_factory_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=520730:520767
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=521121:521163

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

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

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