From: jose.perez.carranza@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Add lzip test instead of iptables for runtime
Date: Thu, 6 Jul 2017 14:03:06 -0700 [thread overview]
Message-ID: <cover.1499373694.git.jose.perez.carranza@linux.intel.com> (raw)
From: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>
This series is created to replace iptables tests for lzip test and avoid conflicts with images built with “musl”. A two separate patches were sent before related to this, one for SDK [1] and other one to add changes to testimage.bbclass[2], the second one itself doe not works, hence in this series the second patch is included and also the complement fully apply the test on runtime.
Patch [1] is still applicable and does not conflicts with this series.
1- https://patchwork.openembedded.org/patch/141496/
2- https://patchwork.openembedded.org/patch/141620/
The following changes since commit 754c03006943a219ffd417c36ab909b464f57f67:
local.conf.sample: drop image-swab reference (2017-07-06 15:03:10 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib jperez/bug11713
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jperez/bug11713
Jose Perez Carranza (1):
oeqa/runtime: Replace buildiptables for buildlzip on runtime tests
Khem Raj (1):
testimage: Use the renamed buildlzip
meta/classes/testimage.bbclass | 6 +++---
meta/lib/oeqa/runtime/cases/{buildiptables.py => buildlzip.py} | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
rename meta/lib/oeqa/runtime/cases/{buildiptables.py => buildlzip.py} (89%)
--
2.12.0
next reply other threads:[~2017-07-06 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 21:03 jose.perez.carranza [this message]
2017-07-06 21:03 ` [PATCH 1/2] oeqa/runtime: Replace buildiptables for buildlzip on runtime tests jose.perez.carranza
2017-07-06 21:03 ` [PATCH 2/2] testimage: Use the renamed buildlzip jose.perez.carranza
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=cover.1499373694.git.jose.perez.carranza@linux.intel.com \
--to=jose.perez.carranza@linux.intel.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