All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: ptest with BBCLASSEXTEND
Date: Fri, 17 May 2019 12:22:08 -0400	[thread overview]
Message-ID: <20190517162208.GA9052@joraj-alpa> (raw)
In-Reply-To: <69efb132247d1706c6c23262ea59e80f75e96768.camel@linuxfoundation.org>

> Its not fast to parse this creates about 59 variants of the image. Its
> (ab)using the mcextend class to an image and add the ptest to that
> image for each ptest in the PTESTS_SLOW and PTESTS_FAST variables. It
> also adds openssh since we need an ssh client in the images for
> testimage to work. I also had to add extra space and memory to the
> image config so all the tests could work.
> 
> You can get a list of the target images with:
> 

For the non-initiated, you will need to have the following in your local.conf
for this to work.

DISTRO_FEATURES_append = " ptest"

That said, I should be able to take a look at the problem related to
lttng-tools.

Thanks

-- 
Jonathan Rajotte-Julien
EfficiOS


      parent reply	other threads:[~2019-05-17 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 10:54 ptest with BBCLASSEXTEND Richard Purdie
2019-05-16 12:36 ` Richard Purdie
2019-05-16 21:13   ` Randy MacLeod
2019-05-16 22:28     ` richard.purdie
2019-05-21 22:31       ` Richard Purdie
2019-06-03  3:10         ` Changqing Li
2019-06-03 13:02           ` richard.purdie
2019-05-22 22:28       ` Jonathan Rajotte-Julien
2019-05-22 22:33         ` richard.purdie
2019-05-17  1:58     ` Changqing Li
2019-05-17 16:22 ` Jonathan Rajotte-Julien [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=20190517162208.GA9052@joraj-alpa \
    --to=jonathan.rajotte-julien@efficios.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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.