W dniu 11.03.2012 13:51, Fathi Boudra pisze:
Hi,
On 11 March 2012 14:40, Zygmunt Krynicki wrote:
I've just realized that we'll likely see issues when test images start
showing up as armhf. Our master image compiler that builds a few of the
tests is going to target armel.
I'd like to propose that we re-purpose the master image. I'd like to _stop_
using it for building software. That is: all lava-test install steps will be
invoked in the _test_ image.
We can apply this without requesting our users to rewrite their test
scenario definitions. I'd like to propose rewriting the scenario file to
invoke any lava-test-install _after_ the boot test image step.
I should hit this issue... very soon, we have preview armhf images
targeting PandaBoard.
I have a blueprint to hook those images to LAVA, still based on
rootfs/hwpack (pre-built images coming soon).
Thanks for the update. I think we assumed too much about our master
images. We should do more in the test image. I'd like to also tag tests
that require building software somehow so that we can at least see how
many tests are affected. If this is a large portion then perhaps we
should look closer at how lava-test should abstract building so that
other parts of the stack (above) know about it.
Thanks
ZK
--
Zygmunt Krynicki
Linaro Validation Team
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
