Automatically adding ccs based on suspected regression changelists:

Create a fuzzer for ComfortNoiseDecoder by henrik.lundin@webrtc.org - https://webrtc.googlesource.com/src/+/5dcbbfd1533bf14efee5b6bd2b879d515d1095c5

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

I'll take a look.

The following revision refers to this bug:
  https://webrtc.googlesource.com/src.git/+/8fabab15097a2e4b913e05a3b04722b457896fa1

commit 8fabab15097a2e4b913e05a3b04722b457896fa1
Author: Henrik Lundin <henrik.lundin@webrtc.org>
Date: Fri Mar 09 13:16:44 2018

CNG fuzzer: avoid long fuzzer runs by limiting generator calls

The number of calls to ComfortNoiseDecoder::Generate() was determined
by the fuzzer input, and was chosen between 0 and 255. This would
sometimes lead to very long runs, with questionable merit. With this
change, the number of call to Generate() is limited to 17 (an
arbitrary small integer).

Bug:  chromium:820078 
Change-Id: I27b5c7f0b72d53370d002a6b157d4451079a0ba9
Reviewed-on: https://webrtc-review.googlesource.com/60941
Reviewed-by: Alex Loiko <aleloi@webrtc.org>
Commit-Queue: Henrik Lundin <henrik.lundin@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#22360}
[modify] https://crrev.com/8fabab15097a2e4b913e05a3b04722b457896fa1/test/fuzzers/comfort_noise_decoder_fuzzer.cc

ClusterFuzz has detected this issue as fixed in range 542189:542199.

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

Fuzzer: libFuzzer_comfort_noise_decoder_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  comfort_noise_decoder_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=522408:522414
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=542189:542199

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

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

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