Well, try it but I'm not sure I understand where the issue is. When we compile test binaries, it'sfrom a cheroot of the test image.
- Paul Larson On Mar 11, 2012 7:51 AM, "Fathi Boudra" <[email protected]> wrote: > 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). > > _______________________________________________ > linaro-validation mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/linaro-validation >
_______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
