On Thu, 2015-04-23 at 14:25 +0100, Paul Eggleton wrote: > On Thursday 23 April 2015 16:02:45 Burton, Ross wrote: > > On 23 April 2015 at 12:20, Paul Eggleton <paul.eggle...@linux.intel.com> > > wrote: > > > I can't remember for certain, but I suspect the lack of this dependency > > > was intentional, so that you could e.g. copy in an image built elsewhere > > > and run tests on it. Maybe we can take the decision we don't need that, > > > but it should be a conscious decision. > > > > My guess was that the missing dependency was from when rootfs always > > regenerated an image, so if you were iterating the test suite it would > > always rebuild the image. This isn't the case now. > > I don't believe so since that change was made prior to testimage's existence > (although it was only a month or so before). > > > Someone should speak with QA and see if they actually use the ability to > > copy in images. Cristian, I'm looking at you. :) > > I'm assuming our QA team aren't the only people that use testimage ;)
This was discussed long ago and there are two different tasks as a compromise. testimage_auto runs automatically after a rootfs is built and has the correct dependencies. "testimage" is triggered manually. The autobuilder actually uses testimage so it can be explicit about which images get tested. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
