Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 22/22] testimage: Use the renamed buildlzip
Date: Thu, 6 Jul 2017 10:34:46 -0500	[thread overview]
Message-ID: <48ec40d9-45ec-a6c1-add5-e389819f6e07@linux.intel.com> (raw)
In-Reply-To: <3107cc24993f111ff2d5714213bd85ff15173221.1499351361.git.raj.khem@gmail.com>


On 07/06/2017 09:33 AM, Khem Raj wrote:
> buildiptables has been replaced with buildlzip
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>   meta/classes/testimage.bbclass | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
> index 6fa2d6fd9f..0c4a84e111 100644
> --- a/meta/classes/testimage.bbclass
> +++ b/meta/classes/testimage.bbclass
> @@ -49,10 +49,10 @@ DEFAULT_TEST_SUITES_pn-core-image-x11 = "${MINTESTSUITE}"
>   DEFAULT_TEST_SUITES_pn-core-image-lsb = "${NETTESTSUITE} pam parselogs ${RPMTESTSUITE}"
>   DEFAULT_TEST_SUITES_pn-core-image-sato = "${NETTESTSUITE} connman xorg parselogs ${RPMTESTSUITE} \
>       ${@bb.utils.contains('IMAGE_PKGTYPE', 'rpm', 'python', '', d)}"
> -DEFAULT_TEST_SUITES_pn-core-image-sato-sdk = "${NETTESTSUITE} buildcpio buildiptables buildgalculator \
> +DEFAULT_TEST_SUITES_pn-core-image-sato-sdk = "${NETTESTSUITE} buildcpio buildlzip buildgalculator \
>       connman ${DEVTESTSUITE} logrotate perl parselogs python ${RPMTESTSUITE} xorg"
>   DEFAULT_TEST_SUITES_pn-core-image-lsb-dev = "${NETTESTSUITE} pam perl python parselogs ${RPMTESTSUITE}"
> -DEFAULT_TEST_SUITES_pn-core-image-lsb-sdk = "${NETTESTSUITE} buildcpio buildiptables buildgalculator \
> +DEFAULT_TEST_SUITES_pn-core-image-lsb-sdk = "${NETTESTSUITE} buildcpio buildlzip buildgalculator \
>       connman ${DEVTESTSUITE} logrotate pam parselogs perl python ${RPMTESTSUITE}"
>   DEFAULT_TEST_SUITES_pn-meta-toolchain = "auto"
>   
> @@ -61,7 +61,7 @@ DEFAULT_TEST_SUITES_remove_aarch64 = "xorg"
>   
>   # qemumips is quite slow and has reached the timeout limit several times on the YP build cluster,
>   # mitigate this by removing build tests for qemumips machines.
> -MIPSREMOVE ??= "buildcpio buildiptables buildgalculator"
> +MIPSREMOVE ??= "buildcpio buildlzip buildgalculator"
>   DEFAULT_TEST_SUITES_remove_qemumips = "${MIPSREMOVE}"
>   DEFAULT_TEST_SUITES_remove_qemumips64 = "${MIPSREMOVE}"
>   
I think this patch is not applicable as for runtime tests 
(meta/lib/oeqa/runtime/cases/) we do actually use buildiptables test, 
for sdk test there are not filters so in the case of using "testsdk" all 
the available test under meta/lib/oeqa/sdk/cases should be executed.

-- 
Saludos
José



  reply	other threads:[~2017-07-06 15:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 14:33 [PATCH 00/22] Glibc 2.26 update and musl updates Khem Raj
2017-07-06 14:33 ` [PATCH 01/22] gcc: Introduce a knob to configure gcc to default to PIE Khem Raj
2017-07-06 14:33 ` [PATCH 02/22] security_flags.inc: Delete pinnings for SECURITY_NO_PIE_CFLAGS Khem Raj
2017-07-06 14:33 ` [PATCH 03/22] distutils, setuptools: Delete use of SECURITY_NO_PIE_CFLAGS Khem Raj
2017-07-06 14:33 ` [PATCH 04/22] gcc7: Enable static PIE Khem Raj
2017-07-06 14:33 ` [PATCH 05/22] gcc: Link libssp_nonshared.a only on musl targets Khem Raj
2017-07-06 14:33 ` [PATCH 06/22] sysklogd: Improve build and fix runtime crash Khem Raj
2017-07-06 14:33 ` [PATCH 07/22] libunwind: We set -fPIE in security flags now if gcc is not configured for default PIE Khem Raj
2017-07-06 14:33 ` [PATCH 08/22] gstreamer1.0-plugins-bad: Fix missing library with bcm egl Khem Raj
2017-07-06 14:33 ` [PATCH 09/22] security_flags.inc: Do not build gcc for powerpc with PIE defaults Khem Raj
2017-07-06 14:33 ` [PATCH 10/22] ovmf: Fix build with toolchain defaulting to PIE Khem Raj
2017-07-06 14:33 ` [PATCH 11/22] glibc: Upgrade to 2.25.90 Khem Raj
2017-07-06 14:33 ` [PATCH 12/22] glibc: Drop obsoleted bits/string.h from multilibbing Khem Raj
2017-07-06 14:33 ` [PATCH 13/22] glibc: Enable obsoleted nsl Khem Raj
2017-07-06 14:33 ` [PATCH 14/22] gcc-sanitizer: Fix build with glibc 2.26 Khem Raj
2017-07-06 14:33 ` [PATCH 15/22] gcc: Use ucontext_t instead of ucontext Khem Raj
2017-07-06 14:33 ` [PATCH 16/22] gcc: Fix libssh_nonshared linker specs for ppc/musl Khem Raj
2017-07-06 14:33 ` [PATCH 17/22] musl: Update to latest on master Khem Raj
2017-07-06 14:33 ` [PATCH 18/22] world-broken.inc: Remove packages which are now buildable on musl Khem Raj
2017-07-06 14:33 ` [PATCH 19/22] valgrind: tests build fixes for musl Khem Raj
2017-07-06 14:33 ` [PATCH 20/22] mpeg2dec: Fix textrels QA errors on arm Khem Raj
2017-07-06 14:33 ` [PATCH 21/22] oeqa/sdk: Replace buildiptables for buildlzip tests Khem Raj
2017-07-06 14:33 ` [PATCH 22/22] testimage: Use the renamed buildlzip Khem Raj
2017-07-06 15:34   ` Jose Perez Carranza [this message]
2017-07-06 15:40     ` Khem Raj
2017-07-06 16:05       ` Jose Perez Carranza
2017-07-06 16:05         ` Khem Raj
2017-07-06 21:09   ` Jose Perez Carranza
2017-07-06 15:01 ` ✗ patchtest: failure for Glibc 2.26 update and musl updates Patchwork

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=48ec40d9-45ec-a6c1-add5-e389819f6e07@linux.intel.com \
    --to=jose.perez.carranza@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox