Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically adding ccs based on suspected regression changelists:

Delete method DecoderDatabase::RegisterPayload(...NetEqDecoder...) by nisse@webrtc.org - https://webrtc.googlesource.com/src/+/0554368eedf987c317eb29544f42a44baa2388ba

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

I can repro this locally, investigating.

See https://webrtc-review.googlesource.com/c/src/+/117261

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

commit 5d7cf3d4ebee5a4f30b3e586bc249cede8adbb34
Author: Niels Möller <nisse@webrtc.org>
Date: Mon Jan 14 12:24:02 2019

Fix RTC_CHECK in neteq_rtp_fuzzer

The change in
https://webrtc-review.googlesource.com/c/116683 made the fuzzer crash
at startup.

Bug:  chromium:921050 ,  webrtc:10185 
Change-Id: Ie3eb26e12b4ae9b29c1c424af0d3eb287b5f1a73
Reviewed-on: https://webrtc-review.googlesource.com/c/117261
Commit-Queue: Niels Moller <nisse@webrtc.org>
Reviewed-by: Karl Wiberg <kwiberg@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#26238}
[modify] https://crrev.com/5d7cf3d4ebee5a4f30b3e586bc249cede8adbb34/test/fuzzers/neteq_rtp_fuzzer.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/93dd9f97ac8b275f7e23bb99e0c3f0cfb98d8b67

commit 93dd9f97ac8b275f7e23bb99e0c3f0cfb98d8b67
Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Date: Tue Jan 15 03:01:45 2019

Roll src/third_party/webrtc b2e21b014c3d..dcfe484f2e12 (14 commits)

https://webrtc.googlesource.com/src.git/+log/b2e21b014c3d..dcfe484f2e12


git log b2e21b014c3d..dcfe484f2e12 --date=short --no-merges --format='%ad %ae %s'
2019-01-14 mbonadei@webrtc.org Remove definition of macro WEBRTC_THREAD_RR (it's unused).
2019-01-14 andersc@webrtc.org Remove legacy video codec factories.
2019-01-14 danilchap@webrtc.org Publish rtc::QueuedTask in api as webrtc::QueuedTask
2019-01-14 titovartem@webrtc.org Introduce Y4mFrameReader.
2019-01-14 kwiberg@webrtc.org RefCounter::DecRef: Remove obsolete TODO and update comment
2019-01-14 titovartem@google.com Add extra documentation and minor fixes into video quality analyzer
2019-01-14 ilnik@webrtc.org Introduce DecodedFramesHistory class and use it in FrameBuffer
2019-01-14 nisse@webrtc.org Refactor WebRtcVideoEngine tests to not use cricket::VideoCapturer, part 1.
2019-01-14 nisse@webrtc.org Fix RTC_CHECK in neteq_rtp_fuzzer
2019-01-14 nisse@webrtc.org Delete StreamInterface methods GetPosition, SetPosition and Rewind
2019-01-14 mbonadei@webrtc.org Remove explicit -fsanitize=memory from BUILD.gn.
2019-01-14 mbonadei@webrtc.org Remove deprecated code from logging.
2019-01-14 titovartem@webrtc.org Add new owners to the test/ directory.
2019-01-14 srte@webrtc.org Adds nisse@ and sprang@ to test/OWNERS


Created with:
  gclient setdep -r src/third_party/webrtc@dcfe484f2e12

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng

BUG=chromium:None,chromium:921050,chromium:None,chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I6b683c2743df40f971541962680a080ad2647c66
Reviewed-on: https://chromium-review.googlesource.com/c/1409599
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#622701}
[modify] https://crrev.com/93dd9f97ac8b275f7e23bb99e0c3f0cfb98d8b67/DEPS

ClusterFuzz has detected this issue as fixed in range 622684:622701.

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

Fuzzer: libFuzzer_neteq_rtp_fuzzer
Fuzz target binary: neteq_rtp_fuzzer
Job Type: x86_libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x002edfe5
Crash State:
  webrtc::test::FuzzOneInputTest
  webrtc_fuzzer_main.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=621964:621970
Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan&range=622684:622701

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6268163066691584 is verified as fixed, so closing issue as verified.

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