Add a copy of the "WinClang64 (dbg)" bot to the main waterfall.

scripts/slave/recipe_modules/chromium_tests/chromium_win.py

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 from . import steps
 
 SPEC = {
   'settings': {
     'build_gs_bucket': 'chromium-win-archive',
     # WARNING: src-side runtest.py is only tested with chromium CQ builders.
@@ skipping 264 matching lines @@
       'test_generators': [
         steps.generate_gtest,
         steps.generate_script,
         steps.generate_isolated_script,
       ],
       'enable_swarming': True,
       'testing': {
         'platform': 'win',
       },
     },
+    'WinClang': {

[Dirk Pranke, 2016/04/15 18:26:27]

If this is a debug x64 bot, it seems like it would be less confusing to call
this 'Win Clang x64 (dbg)' ?

[Nico, 2016/04/15 18:28:03]

Hm, the reasoning behind the current name is that I'd like to be able to change
the configuration of the bot if necessary (between debug/release, component/not
component etc), and if the config is in the name that's close to impossible
since the try waterfall refers to this bot by name.

+      'chromium_config': 'chromium_win_clang',
+      'chromium_apply_config': ['mb'],
+      'gclient_config': 'chromium',
+      'chromium_config_kwargs': {
+        'BUILD_CONFIG': 'Debug',
+        'TARGET_PLATFORM': 'win',
+        'TARGET_BITS': 64,
+      },
+      'compile_targets': [
+        'all',
+      ],
+      # Recipes builds Debug builds with component=shared_library by default.
+      'bot_type': 'builder',
+      'testing': {
+        'platform': 'win',
+      },
+      'use_isolate': True,
+      'enable_swarming': True,
+      # Workaround so that recipes doesn't add random build targets to our
+      # compile line. We want to build everything.
+      'add_tests_as_compile_targets': False,
+    },
   },
 }