<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 23 April 2015 at 19:47, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":5hq" class="a3s" style="overflow:hidden">This was discussed long ago and there are two different tasks as a<br>
compromise. testimage_auto runs automatically after a rootfs is built<br>
and has the correct dependencies. "testimage" is triggered manually. The<br>
autobuilder actually uses testimage so it can be explicit about which<br>
images get tested.</div></blockquote></div><br>The use-case was Cristi editing a recipe and running bitbake myimage -c testimage with the expectation that the image gets rebuilt before testing. This isn't unreasonable at currently the only way to do this is bitbake myimage && bitbake myimage -c testimage.</div><div class="gmail_extra"><br></div><div class="gmail_extra">If testimage_auto is merged with testimage I presume there'll be some variable to control the behaviour. Could we extend it to have an option to make the image depend on the rootfs generation to cover all three use-cases?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>