summaryrefslogtreecommitdiff
path: root/android/lava-android-test-host.yaml
AgeCommit message (Collapse)Author
2015-10-05Android: Multinode target side unificationMilosz Wasilewski
CTS and lava-android-test shared almost the same target side YAML files. This change merges both files into one and adds support for USB only devices. To preserve backward compatibility symilnks were created. These should be considered as deprecated and will be removed after all templates are migrated to new YAML files. Change-Id: Ie47eefb2ee5d1872a96925d3d0ec72501ed8fd71 Signed-off-by: Milosz Wasilewski <milosz.wasilewski@linaro.org>
2015-04-10android: install libraries to support running 32bit ELF on KVMYongqin Liu
in the cts android.host.security package test, it will run the 32bit binary sepolicy-analyze on the host side, so we need to install these libraries to support the 32bit binary running on the 64bit KVM node. Change-Id: Id0ceb2c340af93aa7b5436735c163eed5d5b8087 Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org>
2015-02-25android: fixed lava-android-test-host setupMilosz Wasilewski
Python setuptools v12 is required to install lava-android-test. This was failing in 14.04 Ubuntu image. Fixed with workaround to upgrade setuptools in the install section. Change-Id: I81e988fe29e333aca02c754f9cc1b008ecdd2da1 Signed-off-by: Milosz Wasilewski <milosz.wasilewski@linaro.org>
2015-01-23Revert "lava-android-test-host : adb root"Milosz Wasilewski
This reverts commit d98585e53548f4568deeaa133862578004b8b0ec.
2015-01-21lava-android-test-host : adb rootNaresh Kamboju
With the latest version of Android 5.0.x, the device has to be connected with adb root and followed by adb connect $IP-ADDR to have root access. Change-Id: I4146a01cacba630c65d3afb57415988069b598ec Signed-off-by: Naresh Kamboju <naresh.kamboju@linaro.org>
2014-07-22android: added lava-android-test wrapperMilosz Wasilewski
The lava-test-shell wrapper around lava-android-test allows to execute the lava-android-test from the KVM device type in LAVA which acts as a host. With this approach it is possible to controll the host environment and for example use different Java versions with different Android CTS branches. The test wrapper JSON fragment follows: { "command": "lava_test_shell", "parameters": { "role": "host", "testdef_repos": [ { "git-repo": "git://git.linaro.org/qa/test-definitions.git", "parameters": { "TEST_NAME": "cts", "TEST_PARAMS": "--package android.bionic --timeout 1800 --disable-reboot" }, "testdef": "android/lava-android-test-host.yaml" } ], "timeout": 7200 } }, { "command": "lava_test_shell", "parameters": { "role": "target", "testdef_repos": [ { "git-repo": "git://git.linaro.org/qa/test-definitions.git", "parameters": { "TEST_NAME": "cts", "TEST_PARAMS": "--package android.bionic --timeout 1800 --disable-reboot" }, "testdef": "android/lava-android-test-target.yaml" } ], "timeout": 7200 } } lava-android-test-host.yaml and lava-android-test-target.yaml take TEST_NAME and TEST_PARAMS. These have to be the same for each pair of test shells. Optionally lava-android-test-host.yaml takes JAVA_PACKAGE parameter which is used to define the Java version running on host. Change-Id: Ief169010a1510392c741513136cbc245ab769b7b Signed-off-by: Milosz Wasilewski <milosz.wasilewski@linaro.org>