From: Nathan Lynch <Nathan_Lynch@mentor.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: run ptest for specific packages or layers
Date: Tue, 3 Feb 2015 16:30:07 -0600 [thread overview]
Message-ID: <54D14BEF.5040509@mentor.com> (raw)
In-Reply-To: <CAJTo0LYD0B91NSZ=NC=ZKemczYkkKKQvjnvsmfKqT0tz4C28zQ@mail.gmail.com>
On 01/30/2015 09:09 AM, Burton, Ross wrote:
>
> On 30 January 2015 at 13:39, Markus Boos <Markus.Boos@kistler.com
> <mailto:Markus.Boos@kistler.com>> wrote:
>
> We faced the problem that our image (built with ptest feature)
> doesn't fit into our flash [1].
> I'd like to run the ptest on real hardware cause some packages need
> the mounted FPGA functionality.
>
>
> Don't use ptest-pkgs to pull the tests into the image, but add the ones
> you want directly. Such as:
>
> CORE_IMAGE_EXTRA_INSTALL_append = " ptest-runner myapp-ptest"
Incidentally, I tried this for lttng-tools:
DISTRO_FEATURES_append = " ptest"
CORE_IMAGE_EXTRA_INSTALL_append = " ptest-runner lttng-tools-ptest"
lttng-tools' test script invokes the "prove" command, which does not get
installed:
root@qemuarm:/usr/lib/lttng-tools/ptest# ./run-ptest
[...]
./run.sh unit_tests
./run.sh: line 22: prove: command not found
Makefile:664: recipe for target 'installcheck-am' failed
The "prove" command appears to be provided by perl-misc, so I added that
and retried:
./run.sh unit_tests
Can't locate App/Prove.pm in @INC (you may need to install the
App::Prove module)
Adding perl-modules apparently pulled in the necessary module and got
the tests running.
lttng-tools_2.5.3.bb currently has:
RDEPENDS_${PN}-ptest += "make perl bash"
Should it specify perl-misc and perl-modules instead of just perl?
next prev parent reply other threads:[~2015-02-03 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 13:39 run ptest for specific packages or layers Markus Boos
2015-01-30 15:09 ` Burton, Ross
2015-02-03 22:30 ` Nathan Lynch [this message]
2015-02-04 10:48 ` 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=54D14BEF.5040509@mentor.com \
--to=nathan_lynch@mentor.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 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.