Automatically adding ccs based on suspected regression changelists:

AEC-m and AEC-2 fuzzing. by aleloi@webrtc.org - https://webrtc.googlesource.com/src/+/ab20a6016c5d0798a00dd566c78f5f49065a9492

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

[Triage] Alex, seems like it found something.

ClusterFuzz has detected this issue as fixed in range 537973:537987.

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

Fuzzer: libFuzzer_audio_processing_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  WebRtcAgc_ProcessVad
  WebRtcAgc_ProcessDigital
  WebRtcAgc_Process
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=529631:529648
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=537973:537987

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

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

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