* run ptest for specific packages or layers
@ 2015-01-30 13:39 Markus Boos
2015-01-30 15:09 ` Burton, Ross
0 siblings, 1 reply; 4+ messages in thread
From: Markus Boos @ 2015-01-30 13:39 UTC (permalink / raw)
To: 'openembedded-core@lists.openembedded.org'
Hi
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.
What is the best way to proceed?
Extend the ptest class [2] to read in a "local_ptest.conf" which is whitelisting layer or packages where ptest should be built for?
Or is there another solution or proposal how to proceed?
Best regards
Markus
[1]: https://lists.yoctoproject.org/pipermail/automated-testing/2014-September/000077.html
[2]: https://github.com/openembedded/oe-core/blob/master/meta/classes/ptest.bbclass
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: run ptest for specific packages or layers
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
0 siblings, 1 reply; 4+ messages in thread
From: Burton, Ross @ 2015-01-30 15:09 UTC (permalink / raw)
To: Markus Boos; +Cc: openembedded-core@lists.openembedded.org
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On 30 January 2015 at 13:39, Markus Boos <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"
Ross
[-- Attachment #2: Type: text/html, Size: 899 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: run ptest for specific packages or layers
2015-01-30 15:09 ` Burton, Ross
@ 2015-02-03 22:30 ` Nathan Lynch
2015-02-04 10:48 ` Burton, Ross
0 siblings, 1 reply; 4+ messages in thread
From: Nathan Lynch @ 2015-02-03 22:30 UTC (permalink / raw)
To: Burton, Ross; +Cc: openembedded-core@lists.openembedded.org
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: run ptest for specific packages or layers
2015-02-03 22:30 ` Nathan Lynch
@ 2015-02-04 10:48 ` Burton, Ross
0 siblings, 0 replies; 4+ messages in thread
From: Burton, Ross @ 2015-02-04 10:48 UTC (permalink / raw)
To: Nathan Lynch; +Cc: openembedded-core@lists.openembedded.org
[-- Attachment #1: Type: text/plain, Size: 229 bytes --]
On 3 February 2015 at 22:30, Nathan Lynch <Nathan_Lynch@mentor.com> wrote:
> Should it specify perl-misc and perl-modules instead of just perl?
>
Yes, the ptest packages should add all the dependencies they need.
Ross
[-- Attachment #2: Type: text/html, Size: 622 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-02-04 10:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2015-02-04 10:48 ` Burton, Ross
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.