On Tue, May 12, 2015 at 1:40 AM, Paul Eggleton
wrote:
> Hi Andre,
>
> On Monday 11 May 2015 17:34:45 Andre McCurdy wrote:
>> On Wed, Feb 25, 2015 at 7:15 AM, Cristian Iorga
>>
>> wrote:
>> > oe.utils.both_contain() just does a find() on the value
>> > rather than splitting the value and then look
Hi Andre,
On Monday 11 May 2015 17:34:45 Andre McCurdy wrote:
> On Wed, Feb 25, 2015 at 7:15 AM, Cristian Iorga
>
> wrote:
> > oe.utils.both_contain() just does a find() on the value
> > rather than splitting the value and then looking in the
> > list of split items. The result is that if you ad
On Wed, Feb 25, 2015 at 7:15 AM, Cristian Iorga
wrote:
> oe.utils.both_contain() just does a find() on the value
> rather than splitting the value and then looking in the
> list of split items. The result is that if you add a
> feature to MACHINE_FEATURES that itself has a substring
> that matches
On 26 February 2015 at 22:35, Paul Eggleton
wrote:
> Genuine question, which I should have asked last time those files were
> touched
> - how do those tests relate to oe-selftest tests?
>
Looks like they're unrelated. As they're standard unittest modules it
should be fairly simple to teach oe-s
On Thursday 26 February 2015 20:34:36 Burton, Ross wrote:
> On 26 February 2015 at 20:19, Iorga, Cristian
>
> wrote:
> > Can you point me to a tutorial in this kind of test suites?
>
> I sure can, see meta/lib/oe/tests/test_utils.py. Should be fairly obvious.
Genuine question, which I should h
On 26 February 2015 at 20:19, Iorga, Cristian
wrote:
> Can you point me to a tutorial in this kind of test suites?
>
>
I sure can, see meta/lib/oe/tests/test_utils.py. Should be fairly obvious.
Ross
--
___
Openembedded-core mailing list
Openembedded-
Hi Ross,
Can you point me to a tutorial in this kind of test suites?
/Cristian
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, February 26, 2015 10:08 PM
To: Iorga, Cristian
Cc: OE-core
Subject: Re: [OE-core] [PATCH 1/1] meta/lib/oe/utils.py: properly implement
both_contain
On 25 February 2015 at 15:15, Cristian Iorga
wrote:
> oe.utils.both_contain() just does a find() on the value
> rather than splitting the value and then looking in the
> list of split items. The result is that if you add a
> feature to MACHINE_FEATURES that itself has a substring
> that matches o
oe.utils.both_contain() just does a find() on the value
rather than splitting the value and then looking in the
list of split items. The result is that if you add a
feature to MACHINE_FEATURES that itself has a substring
that matches one of the values looked for when building
COMBINED_FEATURES, you
