From: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] oe-tests: Migrate tests from /oe/test to /oeqa/selftest/oe-tests
Date: Tue, 13 Dec 2016 10:53:27 -0600 [thread overview]
Message-ID: <add9f53a-8c35-91a1-9758-62bd7e12766d@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYbCY=ETjx3wdo1nwsDDJCgEZU7F0JfiuP_zZf+tS3F-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On 12/13/2016 10:32 AM, Burton, Ross wrote:
>
> On 13 December 2016 at 16:17, Burton, Ross <ross.burton@intel.com
> <mailto:ross.burton@intel.com>> wrote:
>
> It took over a minute to load a few tests. Do you have any idea
> why the discovery is so slow?
>
>
at my host is very fast the load (1 second)
jgperezc@jgperezc:~/poky-oetest/build$ oe-selftest -r oelib-tests.elf
oelib-tests.license oelib-tests.path oelib-tests.types oelib-tests.utils
2016-12-13 10:48:28,333 - selftest - INFO - Running bitbake -e to get BBPATH
2016-12-13 10:48:29,125 - selftest - INFO - Checking that everything is
in order before running the tests
2016-12-13 10:48:29,833 - selftest - INFO - Running bitbake -p
2016-12-13 10:48:52,181 - selftest - INFO - test runner init'ed like
unittest
2016-12-13 10:48:52,995 - selftest - INFO - Loading tests from:
oeqa.selftest.oelib-tests.elf
2016-12-13 10:48:52,998 - selftest - INFO - Loading tests from:
oeqa.selftest.oelib-tests.license
2016-12-13 10:48:53,000 - selftest - INFO - Loading tests from:
oeqa.selftest.oelib-tests.path
2016-12-13 10:48:53,001 - selftest - INFO - Loading tests from:
oeqa.selftest.oelib-tests.types
2016-12-13 10:48:53,003 - selftest - INFO - Loading tests from:
oeqa.selftest.oelib-tests.utils
2016-12-13 10:48:53,005 - selftest - INFO - Adding: "include
selftest.inc" in local.conf
2016-12-13 10:48:53,005 - selftest - INFO - Adding: "include
bblayers.inc" in bblayers.conf
> Oh, it's because oeselftest does bitbake calls isn't it.
>
> Good news: you don't need to use oeSelfTest at all, the discovery
> works fine with standard unittest.TestCase objects.
>
> Patch incoming. :)
>
Ok, just wondering if oe-selftest -l will also list those test cases ??
> Ross
>
--
Saludos
José
[-- Attachment #2: Type: text/html, Size: 3795 bytes --]
next prev parent reply other threads:[~2016-12-13 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B6EBB6A4080>
2016-11-15 16:24 ` [PATCH v2] oe-tests: Migrate tests from /oe/test to /oeqa/selftest/oe-tests jose.perez.carranza
2016-11-15 17:16 ` Burton, Ross
2016-11-15 18:09 ` Jose Perez Carranza
2016-11-15 19:10 ` FW: " Benjamin Esquivel
2016-11-15 21:11 ` Burton, Ross
2016-11-17 15:26 ` Jose Perez Carranza
2016-11-15 18:39 ` Benjamin Esquivel
2016-12-13 16:17 ` Burton, Ross
2016-12-13 16:32 ` Burton, Ross
2016-12-13 16:53 ` Jose Perez Carranza [this message]
2016-12-13 16:50 ` Burton, Ross
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=add9f53a-8c35-91a1-9758-62bd7e12766d@linux.intel.com \
--to=jose.perez.carranza@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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