On Sun, Apr 14, 2013 at 10:31:55PM +0200, Marcin Juszkiewicz wrote:
W dniu 12.04.2013 22:16, Tyler Baker pisze:
[removed everyone@ to not get Mike complaining again about sending email to >180 people]
We are very happy to announce you that there are new features getting added to validation.linaro.org
In order to serve you better we are trying to collect metadata from lava-test-shell tests that you are running in validation.linaro.org http://validation.linaro.org.
metadata: name: device-tree format: "Lava-Test-Shell Test Definition 1.0" description: "Device tree test to check folder structure."
os:
- ubuntu
Doc says:
Handling Dependencies (Ubuntu)¶
If your test requires some packages to be installed before its run it can express that in the install section with:
install: deps: - linux-libc-dev - build-essential ====
How I can write one test which will cover different distributions with names of dependencies written for each of them?
For example I want to run "hrw-test-umbaumbau" test under Fedora, OpenEmbedded, Ubuntu. It requires working toolchain on device and SLang development headers. Each distro needs other names... Today I would write a copy for each distribution.
There is ongoing to work to push dependency installation to a helper script that is provided by the distro-specific support scripts:
https://code.launchpad.net/~terceiro/lava-dispatcher/modularize-distro-suppo...
Basically, when you list deps p1, p2 and p3, lava will call `lava-install-packages p1 p2 p3` on the target, where lava-install-packages is a script that does the right thing for that distro.
When you have packages with different names, though, this approach does not work. In this case you have to remember that lava-test-shell allows you to run whatever you want on the target, and handle the different cases for each distro in your test script.
In that case, perhaps we could provide a binary called `lava-distro` that prints the name of the distro where the test is being run, so that nobody needs to duplicate distro-detection logic. What do you think?
devices:
- origen
- snowball
- panda
- panda-es
- vexpress
Can I run someone's test on my umbaumba device without making copy of test? With old LAVA I could. With new it looks like I can not. Regression?
this metadata is just informative, aimed at allowing use to collect data about the test definitions, and which devices are supposed to be supported by then. Nothing will stop you from submitting that test to another device.