rtc_include_tests=false in libfuzzer bot

To catch bug like chromium:713179 we don't include rtc tests in the
libfuzzer bot (like chromium does).

BUG=chromium:714531
NOTRY=True

Review-Url: https://codereview.webrtc.org/2836873002
Cr-Commit-Position: refs/heads/master@{#17856}

tools-webrtc/mb/mb_config.pyl

@@ -184,7 +184,7 @@
   # This is the list of configs that you can pass to mb; each config
   # represents a particular combination of gn args that we must support.
   # A given config *may* be platform-specific but is not necessarily so (i.e.,
-  #  we might have mac, win, and linux bots all using the 'release_bot' config).
+  # we might have mac, win, and linux bots all using the 'release_bot' config).
   'configs': {
     # Linux, Mac and Windows
     'gcc_release_bot_x64': [
@@ -236,7 +236,8 @@
       'gn', 'openh264', 'release', 'goma', 'x64'
     ],
     'libfuzzer_asan_release_bot_x64': [
-      'libfuzzer', 'asan', 'optimize_for_fuzzing', 'openh264_release_bot', 'x64'
+      'libfuzzer', 'asan', 'optimize_for_fuzzing', 'openh264_release_bot',
+      'x64', 'no_rtc_tests'
     ],
     'memcheck_release_bot_x64': [
       'memcheck', 'gn', 'openh264_release_bot', 'x64'
@@ -409,6 +410,10 @@
                   'use_prebuilt_instrumented_libraries=true'),
     },
 
+    'no_rtc_tests': {
+      'gn_args': 'rtc_include_tests=false',
+    },
+
     'openh264': {
       'gn_args': 'ffmpeg_branding="Chrome" rtc_use_h264=true',
     },