Don't run AUTest for tryjobs.

That stage doesn't work at the moment because image paths used for tryjobs
aren't structured the same as for non-tryjobs.

BUG=chromium:390828
TEST=Ran a butterfly-paladin trybot with --hwtest turned on.

Change-Id: I8bfa475fc86754bf8e2e0f2b126749d53c599701
Reviewed-on: https://chromium-review.googlesource.com/208795
Commit-Queue: Gabe Black <gabeblack@chromium.org>
Tested-by: Gabe Black <gabeblack@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
diff --git a/cbuildbot/cbuildbot_config.py b/cbuildbot/cbuildbot_config.py
index 2ba5bf3..8d933fb 100755
--- a/cbuildbot/cbuildbot_config.py
+++ b/cbuildbot/cbuildbot_config.py
@@ -102,6 +102,9 @@
           hw_config.pool = constants.HWTEST_TRYBOT_POOL
           hw_config.file_bugs = False
           hw_config.priority = constants.HWTEST_DEFAULT_PRIORITY
+      # TODO: Fix full_release_test.py/AUTest on trybots, crbug.com/390828.
+      my_config['hw_tests'] = [hw_config for hw_config in my_config['hw_tests']
+                               if hw_config.suite != constants.HWTEST_AU_SUITE]
 
     # Default to starting with a fresh chroot on remote trybot runs.
     if options.remote_trybot: