Hi there,
what is the development state of lava-android-test? * last development happen year ago, last tag 2014.01 * not in Linaro's patchwork (https://patches.linaro.org/) * no Debian package (there is empty git repo pkg/lava-android-test.git) * last build isn't in PyPi (well other packages seems to be even pulled from PyPi).
Is it considered as done, or just abandoned? (if yes, why?)
I'm considering to use it for testing Android firmware builds, it looks nice...
Thanks for info.
Kind regards, Petr
PS: I'm sorry to posting to both lists, not sure which one is the right one.
Petr,
On 19 January 2016 at 18:34, Petr Vorel petr.vorel@gmail.com wrote:
Hi there,
what is the development state of lava-android-test?
- last development happen year ago, last tag 2014.01
- not in Linaro's patchwork (https://patches.linaro.org/)
- no Debian package (there is empty git repo pkg/lava-android-test.git)
- last build isn't in PyPi (well other packages seems to be even pulled from
PyPi).
Is it considered as done, or just abandoned? (if yes, why?)
It's not used any more. The main reason (from my perspective) was inability of matching the test results to executed tests. The test that were important to us were migrated to lava-test-shell. Second reason for dropping support for lava-android-test was increasing difficulty in maintaining lava-android-test dependencies on LAVA servers deployed in our LAB. This solution didn't scale well and was abandoned. We have legacy support for lava-android-test in multi node environment if someone still wants to use this code. However my personal recommendation is to move to lava-test-shell.
milosz
I'm considering to use it for testing Android firmware builds, it looks nice...
Thanks for info.
Kind regards, Petr
PS: I'm sorry to posting to both lists, not sure which one is the right one. _______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-validation
Milosz,
It's not used any more. The main reason (from my perspective) was inability of matching the test results to executed tests. The test that were important to us were migrated to lava-test-shell. Second reason for dropping support for lava-android-test was increasing difficulty in maintaining lava-android-test dependencies on LAVA servers deployed in our LAB. This solution didn't scale well and was abandoned. We have legacy support for lava-android-test in multi node environment if someone still wants to use this code. However my personal recommendation is to move to lava-test-shell.
Thanks for a quick answer, I'll have a look into lava-test-shell.
milosz
Kind regards, Petr
On 19 January 2016 at 18:55, Petr Vorel petr.vorel@gmail.com wrote:
Milosz,
It's not used any more. The main reason (from my perspective) was inability of matching the test results to executed tests. The test that were important to us were migrated to lava-test-shell. Second reason for dropping support for lava-android-test was increasing difficulty in maintaining lava-android-test dependencies on LAVA servers deployed in our LAB. This solution didn't scale well and was abandoned. We have legacy support for lava-android-test in multi node environment if someone still wants to use this code. However my personal recommendation is to move to lava-test-shell.
Thanks for a quick answer, I'll have a look into lava-test-shell.
If you still want to use lava-android-test, here is the lava-test-shell for it: https://git.linaro.org/qa/test-definitions.git/blob/HEAD:/android/lava-andro... This test runs on the host side which in our LAB is simulated with KVM. There is a corresponding target that needs to run on the target device. It depends on your target how to connect with adb (using IP or USB). Please note that your target device needs to support at least some minimal shell (busybox should be enough).
milosz
milosz
Kind regards, Petr
linaro-validation@lists.linaro.org
-
Milosz Wasilewski -
Petr Vorel