chromeos: Adds ash_mus_unittests to the main waterfall

testing/buildbot/chromium.chromiumos.json

Index: testing/buildbot/chromium.chromiumos.json
diff --git a/testing/buildbot/chromium.chromiumos.json b/testing/buildbot/chromium.chromiumos.json
index dcef2a67c33e84be5eeef1b7ae4222aa7f66d06f..0381f58cdce9de9fa77e75927c3898e20e741eba 100644
--- a/testing/buildbot/chromium.chromiumos.json
+++ b/testing/buildbot/chromium.chromiumos.json
@@ -43,6 +43,18 @@
         "test": "ash_content_unittests"
       },
       {
+        "args": [
+          "--mus",
+          "--test-launcher-filter-file=../../testing/buildbot/filters/ash_mus_unittests.filter"
+        ],
+        "name": "ash_mus_unittests",

[msw, 2017/04/18 18:35:04]

Should we also be adding the same thing to "Linux ChromiumOS Tests (1)" and/or
"Linux ChromiumOS Tests (dbg)(1)"?

[sky, 2017/04/18 19:09:35]

I added ash_mus_unittests to the same bots as mash_unittests. I suspect the bot
you mention is x11, which this test won't work with (and we don't care about
x11).

[msw, 2017/04/18 19:19:22]

Hmm, presuming x11 and ozone are mutually exclusive, you're right that this
bot's config includes ozone and the others do not.

+        "override_isolate_target": "ash_unittests",
+        "swarming": {
+          "can_use_on_swarming_builders": true
+        },
+        "test": "ash_unittests"
+      },
+      {
         "swarming": {
           "can_use_on_swarming_builders": true
         },