autotest: Put MashLogin in bvt-cq for 3 boards
The mustash team is still fixing GPU initialization code for several
boards. In the mean time we need to get desktopui_MashLogin back into
bvt-cq so it can run on the Chrome PFQ ToT informational bots (since
most of our regressions are chrome changes).
Split out the control files for link, lumpy, veyron_minnie.
Keep the original control file to run in bvt-perbuild so we can verify
that things are fixed on other boards.
BUG=chromium:708002
TEST=test_that desktopui_MashLogin and desktopui_MashLogin.link
Change-Id: I722f9973221fef6ceb17c9e6a80e5eae5e620297
Reviewed-on: https://chromium-review.googlesource.com/469176
Commit-Ready: James Cook <jamescook@chromium.org>
Tested-by: James Cook <jamescook@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
diff --git a/client/site_tests/desktopui_MashLogin/README b/client/site_tests/desktopui_MashLogin/README
new file mode 100644
index 0000000..e1c2888
--- /dev/null
+++ b/client/site_tests/desktopui_MashLogin/README
@@ -0,0 +1,8 @@
+Tests are temporarily limited to a small subset of boards. We're still
+fixing Ozone GPU initialization on mustash. In the mean time it's
+important that we don't regress other parts of mustash login. By
+limiting to a few boards we can get mustash tests on the Chrome PFQ ToT
+informational waterfall, which will catch regressions due to GPU code
+changes in Chrome ToT.
+
+http://crbug.com/708002
diff --git a/client/site_tests/desktopui_MashLogin/control b/client/site_tests/desktopui_MashLogin/control
index 807a6f5..d623a73 100644
--- a/client/site_tests/desktopui_MashLogin/control
+++ b/client/site_tests/desktopui_MashLogin/control
@@ -6,10 +6,6 @@
NAME = "desktopui_MashLogin"
PURPOSE = "Verify chrome --mash (for mustash) starts and logs in."
CRITERIA = "Fails if chrome --mash does not start."
-# Part of bvt-cq so it runs on the Chrome ToT informational builders.
-# Most failures are due to bad chrome CLs. If you need to disable this
-# test please put it back in bvt-perbuild so we can tell from the nightly
-# builds when chrome is good again.
ATTRIBUTES = "suite:bvt-perbuild"
JOB_RETRIES = 2
TIME = "SHORT"
diff --git a/client/site_tests/desktopui_MashLogin/control.link b/client/site_tests/desktopui_MashLogin/control.link
new file mode 100644
index 0000000..8b8fcb5
--- /dev/null
+++ b/client/site_tests/desktopui_MashLogin/control.link
@@ -0,0 +1,33 @@
+# Copyright 2017 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+DEPENDENCIES = "board:link"
+NAME = "desktopui_MashLogin.link"
+AUTHOR = "jamescook@chromium.org, mustash-team@google.com"
+PURPOSE = "Verify chrome --mash (for mustash) starts and logs in."
+CRITERIA = "Fails if chrome --mash does not start."
+# Part of bvt-cq so it runs on the Chrome ToT informational builders.
+# Most failures are due to bad chrome CLs. If you need to disable this
+# test please put it back in bvt-perbuild so we can tell from the nightly
+# builds when chrome is good again.
+ATTRIBUTES = "suite:bvt-cq"
+JOB_RETRIES = 2
+TIME = "SHORT"
+TEST_CATEGORY = "Functional"
+TEST_CLASS = "desktopui"
+TEST_TYPE = "client"
+BUG_TEMPLATE = {
+ 'components': ['Internals>Mus'],
+ 'labels': ['Proj-Mustash'],
+ 'cc': ['mustash-autotest-bugs@google.com'],
+}
+
+DOC = """
+chrome --mash has significant differences in its initialization vs.
+both regular chrome on devices and chrome on Linux desktop. This
+test verifies chrome can start up and log in. If it fails, please contact
+mustash-team@google.com.
+"""
+
+job.run_test('desktopui_MashLogin')
diff --git a/client/site_tests/desktopui_MashLogin/control.lumpy b/client/site_tests/desktopui_MashLogin/control.lumpy
new file mode 100644
index 0000000..b632a24
--- /dev/null
+++ b/client/site_tests/desktopui_MashLogin/control.lumpy
@@ -0,0 +1,33 @@
+# Copyright 2017 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+DEPENDENCIES = "board:lumpy"
+NAME = "desktopui_MashLogin.lumpy"
+AUTHOR = "jamescook@chromium.org, mustash-team@google.com"
+PURPOSE = "Verify chrome --mash (for mustash) starts and logs in."
+CRITERIA = "Fails if chrome --mash does not start."
+# Part of bvt-cq so it runs on the Chrome ToT informational builders.
+# Most failures are due to bad chrome CLs. If you need to disable this
+# test please put it back in bvt-perbuild so we can tell from the nightly
+# builds when chrome is good again.
+ATTRIBUTES = "suite:bvt-cq"
+JOB_RETRIES = 2
+TIME = "SHORT"
+TEST_CATEGORY = "Functional"
+TEST_CLASS = "desktopui"
+TEST_TYPE = "client"
+BUG_TEMPLATE = {
+ 'components': ['Internals>Mus'],
+ 'labels': ['Proj-Mustash'],
+ 'cc': ['mustash-autotest-bugs@google.com'],
+}
+
+DOC = """
+chrome --mash has significant differences in its initialization vs.
+both regular chrome on devices and chrome on Linux desktop. This
+test verifies chrome can start up and log in. If it fails, please contact
+mustash-team@google.com.
+"""
+
+job.run_test('desktopui_MashLogin')
diff --git a/client/site_tests/desktopui_MashLogin/control.veyron_minnie b/client/site_tests/desktopui_MashLogin/control.veyron_minnie
new file mode 100644
index 0000000..1ab8c38
--- /dev/null
+++ b/client/site_tests/desktopui_MashLogin/control.veyron_minnie
@@ -0,0 +1,33 @@
+# Copyright 2017 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+DEPENDENCIES = "board:veyron_minnie"
+NAME = "desktopui_MashLogin.veyron_minnie"
+AUTHOR = "jamescook@chromium.org, mustash-team@google.com"
+PURPOSE = "Verify chrome --mash (for mustash) starts and logs in."
+CRITERIA = "Fails if chrome --mash does not start."
+# Part of bvt-cq so it runs on the Chrome ToT informational builders.
+# Most failures are due to bad chrome CLs. If you need to disable this
+# test please put it back in bvt-perbuild so we can tell from the nightly
+# builds when chrome is good again.
+ATTRIBUTES = "suite:bvt-cq"
+JOB_RETRIES = 2
+TIME = "SHORT"
+TEST_CATEGORY = "Functional"
+TEST_CLASS = "desktopui"
+TEST_TYPE = "client"
+BUG_TEMPLATE = {
+ 'components': ['Internals>Mus'],
+ 'labels': ['Proj-Mustash'],
+ 'cc': ['mustash-autotest-bugs@google.com'],
+}
+
+DOC = """
+chrome --mash has significant differences in its initialization vs.
+both regular chrome on devices and chrome on Linux desktop. This
+test verifies chrome can start up and log in. If it fails, please contact
+mustash-team@google.com.
+"""
+
+job.run_test('desktopui_MashLogin')
