All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] testimage: regenerate rootfs before testing
Date: Thu, 23 Apr 2015 19:47:07 +0100	[thread overview]
Message-ID: <1429814827.26983.119.camel@linuxfoundation.org> (raw)
In-Reply-To: <1828695.sPIXEUjWsd@peggleto-mobl.ger.corp.intel.com>

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.eggleton@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



  reply	other threads:[~2015-04-23 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23  6:39 [PATCH] testimage: regenerate rootfs before testing Cristian Iorga
2015-04-23  9:20 ` Paul Eggleton
2015-04-23 13:02   ` Burton, Ross
2015-04-23 13:25     ` Paul Eggleton
2015-04-23 18:47       ` Richard Purdie [this message]
2015-05-01 20:24         ` Burton, Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1429814827.26983.119.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.