Issue 670036 link

Starred by 1 user

Issue metadata

Status:	Archived
Owner:	jamescook@chromium.org
Closed:	Jan 2017
Cc:	mustash-bugs@google.com
Components:	Internals>Services>WindowService
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	1
Type:	Bug
Proj-Mustash-Testing VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Move autotest desktopui_MashLogin to bvt-cq

Project Member Reported by jamescook@chromium.org, Nov 30 2016

Issue description

If it is stable on wmatrix for a week (which would be Dec 7, 2016).

Use this search page:
https://wmatrix.googleplex.com/unfiltered?hide_missing=True&releases=tot&tests=desktopui_MashLogin

Comment 1 by jamescook@chromium.org, Jan 5 2017

Status: Started (was: Assigned)

The test is green for 2 weeks. It's time to put it in the PFQ.

Project Member

Comment 2 by bugdroid1@chromium.org, Jan 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/829f755153474bc4bfcdecbfbb7f64aaafcc850b

commit 829f755153474bc4bfcdecbfbb7f64aaafcc850b
Author: James Cook <jamescook@chromium.org>
Date: Thu Jan 05 17:24:26 2017

mash: Put desktopui_MashLogin autotest in bvt-cq suite

This test verifies chrome --mash can start up and log in. It exists to
detect chrome initialization problems that only exist on real hardware,
mostly due to using the Ozone DRM graphics implementation.

The goal here is to get the test in the chrome PFQ informational
builders so we can get narrow revision ranges for chrome regressions.

BUG= chromium:670036 
TEST=desktopui_MashLogin

Change-Id: I5af44c479d2618c0f6f7d16b8fec5abc7ef73e09
Reviewed-on: https://chromium-review.googlesource.com/424943
Commit-Ready: Ilja H. Friedel <ihf@chromium.org>
Tested-by: James Cook <jamescook@chromium.org>
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>

[modify] https://crrev.com/829f755153474bc4bfcdecbfbb7f64aaafcc850b/client/site_tests/desktopui_MashLogin/control