Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] selftest/runtime-test.py: Add test for import test from other layers
Date: Wed, 15 Jun 2016 16:16:25 -0500	[thread overview]
Message-ID: <5761C5A9.2020300@linux.intel.com> (raw)
In-Reply-To: <CAMKF1soZoS9fBShVDOdQ31FMijXY4PJ-LAf1dCrXwO+MW5NXoA@mail.gmail.com>



On 06/15/2016 04:05 PM, Khem Raj wrote:
> On Wed, Jun 15, 2016 at 2:01 PM, Mariano Lopez
> <mariano.lopez@linux.intel.com> wrote:
>>
>> On 06/15/2016 03:47 PM, Khem Raj wrote:
>>> On Tue, Jun 14, 2016 at 3:08 PM, Mariano Lopez
>>> <mariano.lopez@linux.intel.com> wrote:
>>>> If we're just running ping/ssh/selftest, can the image be something a lot
>>>> smaller such as core-image-base?
>>>>
>>>> Ross
>>>>
>>>>
>>>> Unfortunately, base or minimal don't have ssh installed, and ssh it is
>>>> required for the runtime tests.
>>>> I could add the ssh to DISTRO_FEATURES but personally I think that is not
>>>> clean. What do you think?
>>> Can ssh be added to images automatically if testing is enabled ?
>>
>> IMO that is not a good practice, because the image being tested is polluted
>> with packages not meant to be there.
> I thought you mentioned that ssh is required for testing, I dont see
> that as polluting.
> and its only added to image with have ptest turned on.

This is for testimage/testexport and there is a TEST_SUITE specific for 
minimal image.

If the resource consumption seems to be the problem; adding ssh to 
minimal or base would trigger the build of a new rootfs/image; in the 
other hand is very likely core-image-sato is already built when running 
this test.


  reply	other threads:[~2016-06-15 21:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1465824701.git.mariano.lopez@linux.intel.com>
2016-06-13 13:32 ` [PATCH 1/1] selftest/runtime-test.py: Add test for import test from other layers mariano.lopez
2016-06-14  9:26   ` Burton, Ross
2016-06-14 22:08     ` Mariano Lopez
2016-06-15 20:47       ` Khem Raj
2016-06-15 21:01         ` Mariano Lopez
2016-06-15 21:05           ` Khem Raj
2016-06-15 21:16             ` Mariano Lopez [this message]
2016-07-25 22:38   ` Burton, Ross
2016-07-26 20:24     ` Mariano Lopez

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=5761C5A9.2020300@linux.intel.com \
    --to=mariano.lopez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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