New issue
Advanced search Search tips

Issue 916367 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
derat@chromium.org
achuith@chromium.org
hidehiko@chromium.org
nya@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

arc.Boot fails on a kevin running a full image

Project Member Reported by bpastene@chromium.org, Dec 19 
$ local_test_runner arc.Boot
2018/12/18 18:24:53 Waiting for DUT to be ready for testing
2018/12/18 18:24:53 Running arc.Boot
2018/12/18 18:24:53 Restarting ui job
2018/12/18 18:24:55 Waiting for org.chromium.SessionManager D-Bus service
2018/12/18 18:24:55 Asking session_manager to enable Chrome testing
2018/12/18 18:24:55 Waiting for Chrome to write its debugging port to /home/chronos/DevToolsActivePort
2018/12/18 18:24:57 Removing cryptohome for testuser@gmail.com
2018/12/18 18:24:57 Finding OOBE DevTools target
2018/12/18 18:24:57 Connecting to Chrome at ws://127.0.0.1:44705/devtools/page/EA524FF96594F22BDD243C4C3F3AB18D
2018/12/18 18:24:57 Waiting for OOBE
2018/12/18 18:25:00 Logging in as user "testuser@gmail.com"
2018/12/18 18:25:00 Waiting for cryptohome for user "testuser@gmail.com"
2018/12/18 18:25:01 Waiting for OOBE to be dismissed
2018/12/18 18:25:02 Waiting for Android boot
2018/12/18 18:27:02 Error: [boot.go:35] Failed to start ARC: Android failed to boot in very early stage: service.adb.tcp.port not set: context deadline exceeded; last error follows: exec: "android-sh": executable file not found in $PATH
2018/12/18 18:27:03 Finished arc.Boot
2018/12/18 18:27:03 --------------------------------------------------------------------------------
2018/12/18 18:27:03 Ran 1 test(s) in 2m9.382s
2018/12/18 18:27:03 1 failed:
2018/12/18 18:27:03   arc.Boot

Here's /etc/lsb-release on the device:
CHROMEOS_RELEASE_APPID={92A7272A-834A-47A3-9112-E8FD55831660}
CHROMEOS_BOARD_APPID={92A7272A-834A-47A3-9112-E8FD55831660}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOOK
CHROMEOS_RELEASE_BOARD=kevin
GOOGLE_RELEASE=11327.0.0-rc2
CHROMEOS_DEVSERVER=http://swarm-cros-885.c.chromeos-bot.internal:8080
CHROMEOS_RELEASE_BUILDER_PATH=kevin-full/R73-11327.0.0-rc2
CHROMEOS_RELEASE_BUILD_NUMBER=11327
CHROMEOS_RELEASE_BRANCH_NUMBER=0
CHROMEOS_RELEASE_CHROME_MILESTONE=73
CHROMEOS_RELEASE_PATCH_NUMBER=0-rc2
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=11327.0.0-rc2 (Continuous Builder - Builder: N/A) kevin
CHROMEOS_RELEASE_BUILD_TYPE=Continuous Builder - Builder: N/A
CHROMEOS_RELEASE_NAME=Chromium OS
CHROMEOS_RELEASE_VERSION=11327.0.0-rc2
CHROMEOS_AUSERVER=http://swarm-cros-885.c.chromeos-bot.internal:8080/update

Comment 1 by derat@chromium.org, Dec 19

Cc: hidehiko@chromium.org nya@chromium.org
Yes, it looks like this (which is a Chrome CQ builder, I think) is using kevin images that don't support ARC -- android-sh is missing and CHROMEOS_ARC_VERSION doesn't appear in /etc/lsb-release.

That seems non-ideal; presumably we want to make sure that Chrome commits don't break these tests.

What does /usr/local/etc/tast_use_flags.txt contain on the DUT?

Comment 3 by bpastene@chromium.org, Dec 19 

> That seems non-ideal; presumably we want to make sure that Chrome commits don't break these tests.

The fact that arc-enabled builds are private (ie: not world-readable) is a bit of a non-starter for chromiums's public bots. We've been discussing how we want to move forward there, but likely won't make any decisions for a bit.

> What does /usr/local/etc/tast_use_flags.txt contain on the DUT?

$ cat /usr/local/etc/tast_use_flags.txt 
# This file is used by the Tast integration testing system to
# determine which software features are present in the system image.
# Don't use it for anything else. Your code will break.
arc
cups
display_backlight
internal_mic
kvm_host
memd
ml_service
rk3399

Comment 4 by derat@chromium.org, Dec 19 

Hmm. That means that the "arc" USE flag was set, which I wouldn't expect for a non-internal build.
►

Sign in to add a comment