All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] testimage: regenerate rootfs before testing
Date: Fri, 1 May 2015 21:24:50 +0100	[thread overview]
Message-ID: <CAJTo0LbBMnBK-mFZCLS40_OJTQTmcJAnoB=yAXTM5zydaNOVAQ@mail.gmail.com> (raw)
In-Reply-To: <1429814827.26983.119.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

On 23 April 2015 at 19:47, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

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

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.

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?

Ross

[-- Attachment #2: Type: text/html, Size: 1415 bytes --]

      reply	other threads:[~2015-05-01 20:25 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
2015-05-01 20:24         ` Burton, Ross [this message]

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='CAJTo0LbBMnBK-mFZCLS40_OJTQTmcJAnoB=yAXTM5zydaNOVAQ@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=richard.purdie@linuxfoundation.org \
    /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.