New issue
Advanced search Search tips

Issue 895215 link

Starred by 2 users
Status: Duplicate
Merged: issue 895337
Owner:
jdufault@chromium.org
Closed: Oct 16
Cc:
josephsih@chromium.org
derat@chromium.org
seobrien@chromium.org
amstan@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

A few platforms: HWTest failed: ui.ChromeLogin

Project Member Reported by josephsih@chromium.org, Oct 15 
https://chromiumos-build-annotator.googleplex.com/build_annotations/edit_annotations/master-paladin/3037056/?num_builds=60&latest_build_id=3037759

Failed platforms included: nyan_kitty, amd64-generic, veyron_speedy, peppy

Stage HWTest [bvt-tast-cq]
tast.ui.ChromeLogin                FAIL: Expected page content "Hooray, it worked!", got ""
TestFailure: ** HWTest failed (code 1) **

A similar  issue 884454  might be relatd. Hi Jacob, are you the right person to take a look? Please help reassign when proper. Thanks!

Comment 2 by jdufault@chromium.org, Oct 16

Cc: derat@chromium.org
derat@, any ideas on why the HTTP server would fail to serve the expected content?

DEBUG:root:[stdout] 2018/10/15 04:32:20 Running ui.ChromeLogin
DEBUG:root:[stdout] 2018/10/15 04:32:20 Waiting for org.chromium.SessionManager D-Bus service
DEBUG:root:[stdout] 2018/10/15 04:32:20 Restarting ui job
DEBUG:root:[stdout] 2018/10/15 04:32:21 Waiting for org.chromium.SessionManager D-Bus service
DEBUG:root:[stdout] 2018/10/15 04:32:21 Asking session_manager to enable Chrome testing
DEBUG:root:[stdout] 2018/10/15 04:32:21 Waiting for Chrome to write its debugging port to /home/chronos/DevToolsActivePort
DEBUG:root:[stdout] 2018/10/15 04:32:22 Checking cryptohomed service
DEBUG:root:[stdout] 2018/10/15 04:32:22 Removing cryptohome for testuser@gmail.com
DEBUG:root:[stdout] 2018/10/15 04:32:22 Finding OOBE DevTools target
DEBUG:root:[stdout] 2018/10/15 04:32:22 Connecting to Chrome at ws://127.0.0.1:40845/devtools/page/2DBC61514A95F792BBD6D7CADC26FCAA
DEBUG:root:[stdout] 2018/10/15 04:32:23 Waiting for OOBE
DEBUG:root:[stdout] 2018/10/15 04:32:28 Logging in as user "testuser@gmail.com"
DEBUG:root:[stdout] 2018/10/15 04:32:29 Waiting for cryptohome for user "testuser@gmail.com"
DEBUG:root:[stdout] 2018/10/15 04:32:36 Waiting for OOBE to be dismissed
DEBUG:root:[stdout] 2018/10/15 04:32:39 Waiting for SessionStateChanged "started" D-Bus signal from session_manager
DEBUG:root:[stdout] 2018/10/15 04:32:39 Got SessionStateChanged signal
DEBUG:root:[stdout] 2018/10/15 04:32:39 Creating new page with URL http://127.0.0.1:41099
DEBUG:root:[stdout] 2018/10/15 04:32:39 Connecting to Chrome at ws://127.0.0.1:40845/devtools/page/2C78DC48A29AEC6163F349B318609418
DEBUG:root:[stdout] 2018/10/15 04:32:40 Got content ""
DEBUG:root:[stdout] 2018/10/15 04:32:40 Error: [chrome_login.go:102] Expected page content "Hooray, it worked!", got ""
DEBUG:root:[stdout] 2018/10/15 04:32:40 Finished ui.ChromeLogin
DEBUG:root:[stdout] 2018/10/15 04:32:40 --------------------------

Comment 3 by derat@chromium.org, Oct 16

Mergedinto: 895337
Status: Duplicate (was: Untriaged)
I think that this is tracked by  issue 895337 . The current theory is that the failures were caused by a race introduced into the test (that's since been reverted).
►

Sign in to add a comment