New issue
Advanced search Search tips
Starred by 4 users
Status: Started
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----

Sign in to add a comment
desktopui_ScreenLocker failing on betty
Project Member Reported by, Dec 6 Back to list
Filed by on behalf of

/tmp/cbuildbotSb9dnC/smoke/test_harness/all/SimpleTestVerify/1_autotest_tests/results-36-desktopui_ScreenLocker                                                                  [  FAILED  ]
/tmp/cbuildbotSb9dnC/smoke/test_harness/all/SimpleTestVerify/1_autotest_tests/results-36-desktopui_ScreenLocker                                                                    FAIL: Screen not locked after using keyboard shortcut
/tmp/cbuildbotSb9dnC/smoke/test_harness/all/SimpleTestVerify/1_autotest_tests/results-36-desktopui_ScreenLocker/desktopui_ScreenLocker                                           [  FAILED  ]
/tmp/cbuildbotSb9dnC/smoke/test_harness/all/SimpleTestVerify/1_autotest_tests/results-36-desktopui_ScreenLocker/desktopui_ScreenLocker                                             FAIL: Screen not locked after using keyboard shortcut

Builders failed on: 
- betty-arc64-nyc-android-pfq:

Status: Assigned
Y'all touched a related bug recently (issue 781845).  Can you help get this one to the right place?
xiaoyinh@ is currently reworking the desktopui_ScreenLocker test to use views-based lock.
Labels: -Pri-1 Pri-0
This is failing pre-CQ runs as well.

If a proper fix is not incoming immediately, can we please get a revert to avoid blocking all other developers.

For example:
Reverted my CL which changed the autotest API.

Labels: -Pri-0 -Sheriff-Chromium Pri-1
Status: Started
Fingers crossed that this is fixed by the revert in comment 6; removing from sheriff queue.
Just noting that a number of builds have continued to fail after the revert, but so far, all of them were started BEFORE the revert.
Labels: -Pri-1 Pri-0
This is still failing, including builds that started post revert.
It's time to remove this test from bvt-cq
Project Member Comment 11 by, Dec 7
The following revision refers to this bug:

commit 4db1324ac3990d2ca0393b64346ef2da7f435c64
Author: Aviv Keshet <>
Date: Thu Dec 07 02:57:57 2017

temporarily remove desktopui_ScreenLocker from smoke suite


Change-Id: Ib86ae0cb2a2ead68a25e92c6702e9e96e2b6eb29
Tested-by: Aviv Keshet <>
Reviewed-by: Hung-Te Lin <>


Labels: -Pri-0 Pri-2
Test removed from smoke, fix at leisure.
When this is fixed, it'd be nice to see some investigation of how it started failing on the CQ. Was it broken by a change to something not exercised by the Chrome OS CQ or Chrome PFQ?
Sign in to add a comment