From: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Francisco Pedraza <francisco.j.pedraza.gonzalez@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Test needed to verify postinst script order.
Date: Thu, 17 Nov 2016 09:33:33 -0600 [thread overview]
Message-ID: <358803d5-7678-9c6e-2017-9007263d02d5@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbxF0sdYqmK3ttUyaiyTPmg+ME9qbSS1NnpcA4H7iQLaQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
On 11/17/2016 06:14 AM, Burton, Ross wrote:
>
> On 16 November 2016 at 00:50, Francisco Pedraza
> <francisco.j.pedraza.gonzalez@intel.com
> <mailto:francisco.j.pedraza.gonzalez@intel.com>> wrote:
>
> Will verify the following:
> 1. Compile a minimal image.
> 2. The compiled image will add the created layer with the
> recipes postinstz postinsta postinstb postinstd postinstp postinstt
> created previously at "meta-selftest/recipes-test"
> 2. Run qemu
> 3. Validate the task execution order.
> V4
>
>
> This is missing the test that some postinsts should be happening at
> rootfs time.
I have assigned the bug 8433 and I will send a different patch to add
those test cases, I'm just waiting to the final implementation of this
patch to be accepted to avoid execution and merge conflicts.
>
> Also, can it permute PACKAGE_CLASSES (rotate through all three
> options) so it exercises all backends.
>
> Signed-off-by: Francisco Pedraza
> <francisco.j.pedraza.gonzalez@intel.com
> <mailto:francisco.j.pedraza.gonzalez@intel.com>>
> ---
> .../recipes-test/postinsta/postinsta_1.0.bb
> <http://postinsta_1.0.bb> | 20 +++++++++++
> .../recipes-test/postinstb/postinstb_1.0.bb
> <http://postinstb_1.0.bb> | 22 ++++++++++++
> .../recipes-test/postinstd/postinstd_1.0.bb
> <http://postinstd_1.0.bb> | 22 ++++++++++++
> .../recipes-test/postinstp/postinstp_1.0.bb
> <http://postinstp_1.0.bb> | 22 ++++++++++++
> .../recipes-test/postinstt/postinstt_1.0.bb
> <http://postinstt_1.0.bb> | 22 ++++++++++++
> .../recipes-test/postinstz/postinstz_1.0.bb
> <http://postinstz_1.0.bb> | 12 +++++++
>
>
> For clarity can all of these be squashed into a single recipe with
> clearer names?
>
> Ross
>
>
[-- Attachment #2: Type: text/html, Size: 4774 bytes --]
next prev parent reply other threads:[~2016-11-17 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 0:50 [PATCH] Test needed to verify postinst script order Francisco Pedraza
2016-11-17 12:14 ` Burton, Ross
2016-11-17 15:33 ` Jose Perez Carranza [this message]
2016-11-17 18:20 ` Pedraza Gonzalez, Francisco J
2016-11-18 12:59 ` 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=358803d5-7678-9c6e-2017-9007263d02d5@linux.intel.com \
--to=jose.perez.carranza@linux.intel.com \
--cc=francisco.j.pedraza.gonzalez@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox