Converted the tryserver.chromium.linux asan builder to a recipe.

scripts/slave/recipe_modules/chromium/tryserver_chromium_linux.py

Index: scripts/slave/recipe_modules/chromium/tryserver_chromium_linux.py
diff --git a/scripts/slave/recipe_modules/chromium/tryserver_chromium_linux.py b/scripts/slave/recipe_modules/chromium/tryserver_chromium_linux.py
new file mode 100644
index 0000000000000000000000000000000000000000..f3de410078f4ccac5ce757176580310480ffff3c
--- /dev/null
+++ b/scripts/slave/recipe_modules/chromium/tryserver_chromium_linux.py
@@ -0,0 +1,60 @@
+# 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 = {
+  'builders': {
+    'Linux ASan LSan Builder': {
+      'recipe_config': 'chromium_asan',
+      'chromium_config_kwargs': {
+         'BUILD_CONFIG': 'Release',
+         'TARGET_BITS': 64,
+      },
+      'bot_type': 'builder_tester',
+      'testing': {'platform': 'linux'},
+      'compile_targets': [

[Michael Achenbach, 2014/08/09 07:57:35]

Look at how chromium_linux_rel is defined:
https://code.google.com/p/chromium/codesearch#chromium/tools/build/scripts/sl...

I don't think you need the compile targets or any tests here. They're all
dynamically calculated. You'll need a chromium-side spec file that lands first -
like this:
http://src.chromium.org/viewvc/chrome/trunk/src/testing/buildbot/chromium_try...
or this:
http://src.chromium.org/viewvc/chrome/trunk/src/testing/buildbot/tryserver.ch...

[Paweł Hajdan Jr., 2014/08/11 10:01:23]

Yes, please use chromium_trybot recipe, *not* the chromium recipe.
This - alternatively feel free to create another spec file for the memory
trybots, e.g. chromium_memory_trybot.json. There is an existing infrastructure
to make chromium_trybot recipe use a different spec file.

[cmumford, 2014/08/13 17:17:07]

Thanks Pawel. I've created a new chromium_memory_trybot.json file because
original asan tests only ran 27 tests, but chromium.memory.json runs 69.
chromium.memory.json is a superset of linux_asan (i.e. all tests are included),
but I just want to make a lateral move over to a recipe and not triple the tests
that are run.

https://codereview.chromium.org/464063004/

When/if that lands can you instruct me how to reference it in by this recipe?

+        'accessibility_unittests',
+        'base_unittests',
+        'cacheinvalidation_unittests',
+        'cast_unittests',
+        'cc_unittests',
+        'components_unittests',
+        'content_unittests',
+        'crypto_unittests',
+        'device_unittests',
+        'display_unittests',
+        'gcm_unit_tests',
+        'gfx_unittests',
+        'google_apis_unittests',
+        'gpu_unittests',
+        'ipc_tests',
+        'jingle_unittests',
+        'media_unittests',
+        'net_unittests',
+        'ppapi_unittests',
+        'printing_unittests',
+        'remoting_unittests',
+        'sandbox_linux_unittests',
+        'sql_unittests',
+        'sync_unit_tests',
+        'ui_unittests',
+        'unit_tests',
+        'url_unittests',
+      ],
+      'tests': [
+        steps.ArchiveBuildStep(
+            'chromium-browser-snapshots',
+            gs_acl='public-read',
+        ),
+        steps.Deps2GitTest(),
+        steps.CheckpermsTest(),
+      ],
+      'testing': {
+        'platform': 'linux',
+      },
+    },
+  },
+}
+