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/+/7dc115f5f84ce2ea43c8c7b0f26e3b896dc19582 (bindings: Generate Chromium-style code for union types.).

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

My CL was just a renaming.

#3 Sorry, this is a dup of issue 771912. It looks like your renaming confused Clusterfuzz.

ClusterFuzz has detected this issue as fixed in range 530514:530541.

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

Fuzzer: libFuzzer_renderer_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  state.connection_initialized in NetworkStateNotifier.h
  blink::NetworkStateNotifier::ConnectionType
  blink::NetworkStateNotifier::IsCellularConnectionType
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=504891:504928
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=530514:530541

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

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.