public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: poky@yoctoproject.org
Cc: paul.eggleton@linux.intel.com,
	openembedded-core@lists.openembedded.org,
	georgex.l.musat@intel.com, benjamin.esquivel@intel.com
Subject: [PATCH 2/3] ptests: Update references to new ptest-runner2.
Date: Thu, 14 Jan 2016 16:27:03 -0600	[thread overview]
Message-ID: <a0064e7a8877fa00724ac15263fd51ee04545bb2.1452808373.git.anibal.limon@linux.intel.com> (raw)
In-Reply-To: <cover.1452808370.git.anibal.limon@linux.intel.com>
In-Reply-To: <cover.1452808370.git.anibal.limon@linux.intel.com>

classes/ptest.bbclass: Now recommends ptest-runner2 instead of
			ptest-runner.
oeqa/runtime/_ptest.py: Now validate if ptest-runner2 is installed.

Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
---
 meta/classes/ptest.bbclass      | 2 +-
 meta/lib/oeqa/runtime/_ptest.py | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/classes/ptest.bbclass b/meta/classes/ptest.bbclass
index fa3561e..c84ca97 100644
--- a/meta/classes/ptest.bbclass
+++ b/meta/classes/ptest.bbclass
@@ -12,7 +12,7 @@ PTEST_ENABLED_class-nativesdk = ""
 PTEST_ENABLED_class-cross-canadian = ""
 RDEPENDS_${PN}-ptest_class-native = ""
 RDEPENDS_${PN}-ptest_class-nativesdk = ""
-RRECOMMENDS_${PN}-ptest += "ptest-runner"
+RRECOMMENDS_${PN}-ptest += "ptest-runner2"
 
 PACKAGES =+ "${@bb.utils.contains('PTEST_ENABLED', '1', '${PN}-ptest', '', d)}"
 
diff --git a/meta/lib/oeqa/runtime/_ptest.py b/meta/lib/oeqa/runtime/_ptest.py
index 0621028..d1e51a4 100644
--- a/meta/lib/oeqa/runtime/_ptest.py
+++ b/meta/lib/oeqa/runtime/_ptest.py
@@ -105,10 +105,10 @@ class PtestRunnerTest(oeRuntimeTest):
     def test_ptestrunner(self):
         self.add_smart_channel()
         (runnerstatus, result) = self.target.run('which ptest-runner', 0)
-        cond = oeRuntimeTest.hasPackage("ptest-runner") and oeRuntimeTest.hasFeature("ptest") and oeRuntimeTest.hasPackage("-ptest") and (runnerstatus != 0)
+        cond = oeRuntimeTest.hasPackage("ptest-runner2") and oeRuntimeTest.hasFeature("ptest") and oeRuntimeTest.hasPackage("-ptest") and (runnerstatus != 0)
         if cond:
             self.install_packages(self.install_complementary("*-ptest"))
-            self.install_packages(['ptest-runner'])
+            self.install_packages(['ptest-runner2'])
 
         (runnerstatus, result) = self.target.run('/usr/bin/ptest-runner > /tmp/ptest.log 2>&1', 0)
         #exit code is !=0 even if ptest-runner executes because some ptest tests fail.
-- 
2.1.4



  parent reply	other threads:[~2016-01-14 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 22:27 [PATCH 0/3] ptest-runner2 C implementation Aníbal Limón
2016-01-14 22:27 ` [PATCH 1/3] ptest-runner2: Add new ptest-runner2 recipe Aníbal Limón
2016-01-14 22:27 ` Aníbal Limón [this message]
2016-01-14 22:27 ` [PATCH 3/3] Update dev-manual to point to the new ptest-runner2 Aníbal Limón
2016-01-18 15:52 ` [PATCH 0/3] ptest-runner2 C implementation Aníbal Limón

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=a0064e7a8877fa00724ac15263fd51ee04545bb2.1452808373.git.anibal.limon@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=benjamin.esquivel@intel.com \
    --cc=georgex.l.musat@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=poky@yoctoproject.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