[OE-core] [PATCH 3/3] image/testimage: Rework auto image test execution

[Paulo Neves]

I can, but some of the patches i sent earlier did not have comments.
Maybe I sent them to the wrong place. Furthermore I sometimes have the
feeling that I may have fixed something which, was not in need of
fixing, meaning wrong assumptions on my part.

This HOSTTOOLS case was a case in point: If a stable version (SUMO)
was released like that, I thought it was me who was doing something
wrong, so I added the ip, ping and ifconfing in my layer.conf and
"fixed" it for my case.

I will try to be more active. I am working on a class for the meson
recipes that appends the exe_wrapper of the .cross file to
qemu-${TARGET_ARCH} so that we can run unittests in the build time.
The idea is to left shift and fail the recipe build if tests fail.


Paulo Neves

On Tue, Jun 19, 2018 at 3:13 PM, Alexander Kanavin
<alex.kanavin at gmail.com> wrote:
> 2018-06-19 16:06 GMT+03:00 Paulo Neves <ptsneves at gmail.com>:
>> I support this patch and I see that one of the problems in sumo is
>> fixed, namely the HOSTTOOLS missing ip and ping.
>> Even so there is one HOSTTOOLS that is missing, ifconfig. As far as I
>> know the automatic network setup scripts of runqemu require ifconfig
>> for 192.168.7.1 tap setting. Without ifconfig the virtual machine
>> cannot be spawned.
>>
>> Also, given the lack of the HOSTTOOLS in the sumo version i have, how
>> is this being tested?
>>
>> I also would like to discuss the possibility of testing u-boot in a
>> virtual machine. I have a setup where I am able to pass to qemu,
>> u-boot.bin as a bios file, and then I am able to boot from tftp
>> enabled qemu network device. This allows for unification of test setup
>> of virtualized and real target booting. Do you have any integration
>> like this in the plans?
>
> Paulo, I would recommend that you prepare the patches for all of these
> things, and send them. Yocto is what you make it, don't expect things
> to get fixed for you by other people.
>
> Alex