From: Scott Garman <scott.a.garman@intel.com>
To: <poky@yoctoproject.org>
Subject: Re: [PATCH 1/3] imagetest-qemu: Allow the task to run after any rootfs is created and also standalone
Date: Fri, 3 Dec 2010 20:58:24 -0800 [thread overview]
Message-ID: <4CF9CA70.9060107@intel.com> (raw)
In-Reply-To: <a3ec07a2417519432c4dc9d64f6f1b0df1169fa4.1291035335.git.rpurdie@linux.intel.com>
On 11/28/2010 06:45 AM, Richard Purdie wrote:
> One bitbake invocation can cause multiple images to be generated. We should test
> each one and we cna do this by running after the rootfs task. Running the tests
> standlone is also still possible with a new separate standlone task.
>
> Signed-off-by: Richard Purdie<rpurdie@linux.intel.com>
Acked-by: Scott Garman <scott.a.garman@intel.com>
(with Jiajun's modification)
> ---
> meta/classes/imagetest-qemu.bbclass | 19 ++++++++++++++-----
> 1 files changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/meta/classes/imagetest-qemu.bbclass b/meta/classes/imagetest-qemu.bbclass
> index 07bdf01..3c1586e 100644
> --- a/meta/classes/imagetest-qemu.bbclass
> +++ b/meta/classes/imagetest-qemu.bbclass
> @@ -1,8 +1,3 @@
> -addtask qemuimagetest before do_build
> -# after do_rootfs
> -do_qemuimagetest[nostamp] = "1"
> -do_qemuimagetest[depends] += "qemu-native:do_populate_sysroot"
> -
> # Test related variables
> # By default, TEST_DIR is created under WORKDIR
> TEST_DIR ?= "${WORKDIR}/qemuimagetest"
> @@ -12,6 +7,20 @@ TEST_TMP ?= "${TEST_DIR}/tmp"
> TEST_SCEN ?= "sanity"
>
> python do_qemuimagetest() {
> + qemuimagetest_main(d)
> +}
> +addtask qemuimagetest before do_build after do_rootfs
> +do_qemuimagetest[nostamp] = "1"
> +do_qemuimagetest[depends] += "qemu-native:do_populate_sysroot"
> +
> +python do_qemuimagetest_standalone() {
> + qemuimagetest_main(d)
> +}
> +addtask qemuimagetest_standalone
> +do_qemuimagetest_standalone[nostamp] = "1"
> +do_qemuimagetest_standalone[depends] += "qemu-native:do_populate_sysroot"
> +
> +python qemuimagetest_main(d) {
> import sys
> import re
> import os
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
next prev parent reply other threads:[~2010-12-04 4:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 12:55 [PATCH 0/3] Poky environment tweaks + imagetest change Richard Purdie
2010-11-28 14:45 ` [PATCH 1/3] imagetest-qemu: Allow the task to run after any rootfs is created and also standalone Richard Purdie
2010-11-30 3:35 ` Xu, Jiajun
2010-12-04 4:58 ` Scott Garman [this message]
2010-12-07 12:33 ` Richard Purdie
2010-11-28 17:39 ` [PATCH 2/3] bitbake: Overhaul environment handling Richard Purdie
2010-11-28 17:42 ` [PATCH 3/3] devshell: Clean up devshell code so this task doesn't polute the global namespace Richard Purdie
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=4CF9CA70.9060107@intel.com \
--to=scott.a.garman@intel.com \
--cc=poky@yoctoproject.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.