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/+/079ad54e478f307f2113feed39863a266709887c (Add HTTP/2 stream dependency info derived from RequestPriority to QUIC client headers).

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

ClusterFuzz has detected this issue as fixed in range 530795:530796.

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

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  frame.packets.Empty() || frame.packets.Max() == frame.largest_acked in quic_ack_
  net::LargestAcked
  net::QuicFramer::ProcessTimestampsInAckFrame
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=528550:528560
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=530795:530796

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

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

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