Hi,
I have managed to solve the error by changing the distribution inside lxc. I put ubuntu and now vts starts.
No I do not know how to finish the test-job when vts is finished. At the end VTS outputs a message like this: vts-tf > [2K10-18 12:47:17 I/ResultReporter: Invocation finished in 4m 42s. PASSED: 0, FAILED: 0, MODULES: 0 of 0
Is there any option to trigger the job to finish when getting a specific string as output?
george
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Monday, October 21, 2019 12:19 To: George Nistor george.n@l4b-software.com Cc: lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] VTS does not start because of the adb
I don't think there is any additional adb setup required for LXC. Did you try downloading adb from Google instead using one from distro? Google offers it here: https://dl.google.com/android/repository/platform-tools_r28.0.0-linux.zip
milosz
On Thu, 17 Oct 2019 at 09:06, George Nistor george.n@l4b-software.com wrote:
I am still having this problem inside the lxc container with 'adb start-server' failed.
Should I define something special in the jinja2 device descriptor regarding adb or in the job to be able to use it?
george
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Wednesday, October 16, 2019 12:59 To: George Nistor george.n@l4b-software.com Cc: lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] VTS does not start because of the adb
George,
I understand what the LAVA job is doing. I'm asking you to check whether there is _any_ adb server running on the host? If there is, the server you're running in a container will not be able to connect to the device.
milosz
On Wed, 16 Oct 2019 at 08:46, George Nistor george.n@l4b-software.com wrote:
Hi Lava users,
My adb is not running on the host but in the lxc container lava creates at runtime. I have tried to put also an: adb kill-server command before starting vts but I got the same error.
The lava log looks like this: <LAVA_SIGNAL_STARTRUN 0_device-helpers 219_1.8.4.1>
- cd /home/android-vts/tools
- adb kill-server
Received signal: <STARTRUN> 0_device-helpers 219_1.8.4.1 Starting test lava.0_device-helpers (219_1.8.4.1) Skipping test definition patterns.
- server not running *
- ./vts-tradefed
Android Vendor Test Suite 9.0_R2 (eng.l4b.20190906.094644) Use "help" or "help all" to get more information on running commands. 10-16 07:30:15 E/adb: ADB server didn't ACK 10-16 07:30:15 E/ddms: 'adb start-server' failed -- run manually if necessary 10-16 07:30:15 E/adb: * failed to start daemon * 10-16 07:30:15 E/adb: error: cannot connect to daemon [udev_trigger-lxc-hikey-test-219-07:30:23] device /dev/bus/usb/001/008 added
george
-----Original Message----- From: Milosz Wasilewski milosz.wasilewski@linaro.org Sent: Tuesday, October 15, 2019 17:11 To: George Nistor george.n@l4b-software.com Cc: lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] VTS does not start because of the adb
Do you have adb server running on the host? If so, please kill it and try again. As with LoTR - there is only one adb server to rule them all :)
milosz
On Tue, 15 Oct 2019 at 15:01, George Nistor george.n@l4b-software.com wrote:
Hello Lava users,
Thanks to Tim Jaaks for previous problem I reported. I managed to configure default external shared folder for the lava lxc container.
However,
I try to run VTS from Lava but after displaying initial string with VTS I get an error saying adb server could not start. I have tried restart, no success. The adb seems to be installed in the container.
Does anyone know how to solve this error?
- ./vts-tradefed
Android Vendor Test Suite 9.0_R2 (eng.l4b.20190906.094644)
Use "help" or "help all" to get more information on running commands.
10-15 13:45:22 E/adb: ADB server didn't ACK
10-15 13:45:22 E/ddms: 'adb start-server' failed -- run manually if necessary
10-15 13:45:22 E/adb: * failed to start daemon *
10-15 13:45:22 E/adb: error: cannot connect to daemon
[udev_trigger-lxc-hikey-test-214-13:45:29] device /dev/bus/usb/001/005 added
The adb is put in tlcx deploy
actions:
deploy:
namespace: tlxc
timeout:
minutes: 5to: lxc
packages:
adb
fastboot
wget
unzip
default-jre
os: debian
george
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users