From: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
"Esquivel, Benjamin" <benjamin.esquivel@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: FW: [PATCH v2] oe-tests: Migrate tests from /oe/test to /oeqa/selftest/oe-tests
Date: Thu, 17 Nov 2016 09:26:23 -0600 [thread overview]
Message-ID: <5ac0063b-061c-13b3-e5d0-42a5e35b7199@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYwVrdCUAXSz0VYKNt0TsETL2aZheVN+qv-HYi8jei6Aw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On 11/15/2016 03:11 PM, Burton, Ross wrote:
>
> On 15 November 2016 at 19:10, Benjamin Esquivel
> <benjamin.esquivel@linux.intel.com
> <mailto:benjamin.esquivel@linux.intel.com>> wrote:
>
> The reason for the migration of the tests is for them to be
> included in the selftest execution. And for that execution, it
> needs to base off of the oeSelfTest class.
>
>
> Sounds like a problem with the discovery if it mandates oeselftest.
> Is there a reason why it can't also execute bare unittests?
>
You are right this is a problem on the suite right now AFAIK there
will pbe a fix for this on oeqa2 framework adding Marian and Anibal to
the loop to give an in put on this.
> Ross
[-- Attachment #2: Type: text/html, Size: 2059 bytes --]
next prev parent reply other threads:[~2016-11-17 15:16 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 [this message]
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
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=5ac0063b-061c-13b3-e5d0-42a5e35b7199@linux.intel.com \
--to=jose.perez.carranza@linux.intel.com \
--cc=benjamin.esquivel@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