From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mariano.lopez@linux.intel.com,
openembedded-core@lists.openembedded.org,
juro.bystricky@intel.com
Subject: Re: [PATCH 0/3] oeqa/runtime: Import custom targets
Date: Mon, 27 Mar 2017 14:38:40 +0100 [thread overview]
Message-ID: <1490621920.13980.265.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1490392540.git.mariano.lopez@linux.intel.com>
On Fri, 2017-03-24 at 15:06 -0700, mariano.lopez@linux.intel.com wrote:
> From: Mariano Lopez <mariano.lopez@linux.intel.com>
>
> This series allows to import custom targets to be used with runtime
> testing.
> Now is possible to have a target in <layer>/lib/oeqa/core/target and
> testimage and testexport can use such target using TEST_TARGET
> variable.
>
> To register a custom target you just need use decorate a target class
> with
> registerTarget, and set "targetName" attribute to the name that will
> be used
> by TEST_TARGET variable.
Unfortunately something about this series break oe-selftest:
https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/229/st
eps/Running%20oe-selftest/logs/stdio
It doesn't do it in isolation, that test run by itself is fine. When
run as part of oe-selftest it breaks though. I did bisect it down to
this series and things have all built fine after I dropped these 3
patches.
So we'll have to figure out what is happening here...
Cheers,
Richard
next prev parent reply other threads:[~2017-03-27 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 22:06 [PATCH 0/3] oeqa/runtime: Import custom targets mariano.lopez
2017-03-24 22:06 ` [PATCH 1/3] oeqa: Remove __init__.py files mariano.lopez
2017-03-24 22:06 ` [PATCH 2/3] oeqa/target: Add decorator to register targets mariano.lopez
2017-03-24 22:06 ` [PATCH 3/3] oeqa/runtime/context.py: Add automatic target loading mariano.lopez
2017-03-27 13:38 ` Richard Purdie [this message]
2017-03-27 15:22 ` [PATCH 0/3] oeqa/runtime: Import custom targets Mariano Lopez
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=1490621920.13980.265.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=juro.bystricky@intel.com \
--cc=mariano.lopez@linux.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