public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Francisco Pedraza <francisco.j.pedraza.gonzalez@intel.com>
Subject: [PATCH 1/1] oeqa/sdkext/devtool: use a smaller module to test node.js functionality
Date: Tue, 13 Sep 2016 14:15:14 +1200	[thread overview]
Message-ID: <225249f90cc234b1c302ac4eb26fa3937e339a09.1473732817.git.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <cover.1473732817.git.paul.eggleton@linux.intel.com>
In-Reply-To: <cover.1473732817.git.paul.eggleton@linux.intel.com>

The "forever" package, despite its innocent description, actually drags
in a surprising number of dependencies and as a result the nodejs test
takes up to 10 minutes as a result. Pick a different example with a much
more reasonable set of dependencies.

Addresses part of [YOCTO #10254].

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
 meta/lib/oeqa/sdkext/devtool.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/sdkext/devtool.py b/meta/lib/oeqa/sdkext/devtool.py
index ba12799..65f41f6 100644
--- a/meta/lib/oeqa/sdkext/devtool.py
+++ b/meta/lib/oeqa/sdkext/devtool.py
@@ -91,7 +91,7 @@ class DevtoolTest(oeSDKExtTest):
     @testcase(1478)
     @skipUnlessPassed('test_devtool_location')
     def test_recipes_for_nodejs(self):
-        package_nodejs = "npm://registry.npmjs.org;name=forever;version=0.15.1"
+        package_nodejs = "npm://registry.npmjs.org;name=winston;version=2.2.0"
         self._run('devtool add %s ' % package_nodejs)
         try:
             self._run('devtool build %s ' % package_nodejs)
-- 
2.5.5



      reply	other threads:[~2016-09-13  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  2:15 [PATCH 0/1] Optimisation for eSDK tests Paul Eggleton
2016-09-13  2:15 ` Paul Eggleton [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=225249f90cc234b1c302ac4eb26fa3937e339a09.1473732817.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=francisco.j.pedraza.gonzalez@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