Openembedded Core Discussions
 help / color / mirror / Atom feed
From: leonardo.sandoval.gonzalez@linux.intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v4 0/2] Skip imagefeature and sstatetest tests depending on distro
Date: Mon, 23 Jan 2017 14:41:13 -0600	[thread overview]
Message-ID: <cover.1485203593.git.leonardo.sandoval.gonzalez@linux.intel.com> (raw)

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>

Originally, the selftests were defined for the 'poky' distro. However, there
are more supported distros, including nodistro, poky-lsb and poky-tiny.
This series just focus on two test cases: imagefeatures and sstatetests.

[YOCTO #8525]

The following changes since commit 4aa6644f92975ded908ef99cf313466e0845e071:

  kernel-fitimage: Use compressed ramdisks in FIT images if available (2017-01-23 12:05:23 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib lsandov1/selftest-imagefeatures-sstatetest-distro-agnostic
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lsandov1/selftest-imagefeatures-sstatetest-distro-agnostic

Leonardo Sandoval (2):
  selftest/imagefeatures: skip weston test if required features are not
    present
  selftest: sstatetests: skip glibc-initial tests in case of non-glibc
    distro

 meta/lib/oeqa/selftest/imagefeatures.py |  6 +++---
 meta/lib/oeqa/selftest/sstate.py        |  1 +
 meta/lib/oeqa/selftest/sstatetests.py   | 25 +++++++++++++++++++------
 3 files changed, 23 insertions(+), 9 deletions(-)

-- 
2.1.4



             reply	other threads:[~2017-01-23 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 20:41 leonardo.sandoval.gonzalez [this message]
2017-01-23 20:41 ` [PATCH v4 1/2] selftest/imagefeatures: skip weston test if required features are not present leonardo.sandoval.gonzalez
2017-01-23 20:41 ` [PATCH v4 2/2] selftest: sstatetests: skip glibc-initial tests in case of non-glibc distro leonardo.sandoval.gonzalez

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.1485203593.git.leonardo.sandoval.gonzalez@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@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