Unable to find the exact suspect hence assigning to //src/testing/OWNERS for help in finding an appropriate owner for this.

That code hasn't changed in forever.

However, despite being an OWNER for //testing, I don't actually know that much about gtest. 

Maybe phajdan.jr@ or inferno@ has a guess ...

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6187444545781760

Fuzzer: inferno_twister
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: UNKNOWN
Crash Address: 0x00000003
Crash State:
  testing::internal::FlagToEnvVar
  testing::internal::BoolFromGTestEnv
  testing::`dynamic initializer for 'FLAGS_gtest_also_run_disabled_tests''
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=windows_syzyasan_content_shell&range=380447:380964

Minimized Testcase (0.00 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95ReCh8WzhAmVv5LTyKIL3udJYSHSsaQ0aJ6XaCj-BigLHYXypjL5MMwmnyznFiRjF_FI9wdMCJq6fyJKcA9G5vbe7dAtGSabkIBuaoiW-WcDwTQBvVyHzYTCGtTHKVx4kIqIGwqqdfUWfkqj21xdr-O7MOTw

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 is verified as fixed, closing issue.

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

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot