From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Max Krummenacher <max.oss.09@gmail.com>
Subject: [dizzy][PATCH 2/2] udev: don't keep ptest testdata laying around
Date: Wed, 25 Mar 2015 23:09:37 +0100 [thread overview]
Message-ID: <1427321377-25844-2-git-send-email-Martin.Jansa@gmail.com> (raw)
In-Reply-To: <1427321377-25844-1-git-send-email-Martin.Jansa@gmail.com>
From: Max Krummenacher <max.oss.09@gmail.com>
Only unpack udev's testdata right before executing the tests and cleanup
afterwards.
udev's testsuite can be used by ptest. However currently the testdata against
which its functionality is tested is installed in the sysroot at udev install
time.
If the sysroot is used with qemu the testdata makes qemu entering an infinite
loop.
http://lists.openembedded.org/pipermail/openembedded-core/2014-September/097098.html
This has already been fixed for the systemd udev flavour.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5664
Signed-off-by: Max Krummenacher <max.oss.09@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
---
meta/recipes-core/udev/udev/add-install-ptest.patch | 2 +-
meta/recipes-core/udev/udev/run-ptest | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-core/udev/udev/add-install-ptest.patch b/meta/recipes-core/udev/udev/add-install-ptest.patch
index 755946a..bfc2e94 100644
--- a/meta/recipes-core/udev/udev/add-install-ptest.patch
+++ b/meta/recipes-core/udev/udev/add-install-ptest.patch
@@ -34,7 +34,7 @@ Upstream-Status: Pending
+ (cd $(top_srcdir) && install $(TESTS) $(DESTDIR)/test)
+ (cd $(top_srcdir) && install test/rule-syntax-check.py $(DESTDIR)/test)
+ (cd $(top_srcdir) && install $(RULES) $(DESTDIR)/rules)
-+ tar -C $(DESTDIR)/test/ -xJf $(top_srcdir)/test/sys.tar.xz
++ cp $(top_srcdir)/test/sys.tar.xz $(DESTDIR)/test/
--- a/test/udev-test.pl 2012-03-18 16:43:36.000000000 +0100
+++ b/test/udev-test.pl 2013-02-18 10:31:29.706357321 +0100
@@ -1459,11 +1459,13 @@
diff --git a/meta/recipes-core/udev/udev/run-ptest b/meta/recipes-core/udev/udev/run-ptest
index c6961ce..0e39806 100644
--- a/meta/recipes-core/udev/udev/run-ptest
+++ b/meta/recipes-core/udev/udev/run-ptest
@@ -1,3 +1,5 @@
#!/bin/sh
+tar -C test/ -xJf test/sys.tar.xz
make -k check-TESTS
+make test-sys-distclean
--
2.3.3
prev parent reply other threads:[~2015-03-25 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 2:25 [dizzy][PATCH] fontcache.bbclass: prepend to PACKAGEFUNCS instead of appending Jonathan Liu
2015-03-25 22:09 ` [dizzy][PATCH 1/2] udev: fix ptest rule syntax check Martin Jansa
2015-03-25 22:09 ` Martin Jansa [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=1427321377-25844-2-git-send-email-Martin.Jansa@gmail.com \
--to=martin.jansa@gmail.com \
--cc=max.oss.09@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox