From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Francisco Pedraza <francisco.j.pedraza.gonzalez@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] oeqa/selftest Adds eSDK test cases to devtool verification.
Date: Fri, 19 Aug 2016 23:49:53 +0100 [thread overview]
Message-ID: <1471646993.16712.60.camel@linuxfoundation.org> (raw)
In-Reply-To: <1471644834.16712.59.camel@linuxfoundation.org>
On Fri, 2016-08-19 at 23:13 +0100, Richard Purdie wrote:
> On Wed, 2016-08-17 at 17:31 -0500, Francisco Pedraza wrote:
> > The covered functions are, install libraries headers, image
> > generation binary feeds and
> > sdk update devtool.
> >
> > Signed-off-by: Francisco Pedraza <
> > francisco.j.pedraza.gonzalez@intel.com>
> > ---
> > meta/lib/oeqa/selftest/eSDK.py | 147
> > +++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 147 insertions(+)
> > create mode 100644 meta/lib/oeqa/selftest/eSDK.py
>
> I do love the idea of this and having more tests but the kernel
> module
> ESDK test fails on ppc and mips:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds
> /911/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips/build
> s/898
and:
https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/builds/649/steps/Running%20oe-selftest/logs/stdio
(sorry!)
Cheers,
Richard
prev parent reply other threads:[~2016-08-19 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 22:30 [PATCH 1/2] oeqa/sdkext: Adds test cases for devtool extensible SDK Francisco Pedraza
2016-08-17 22:31 ` [PATCH 2/2] oeqa/selftest Adds eSDK test cases to devtool verification Francisco Pedraza
2016-08-19 22:13 ` Richard Purdie
2016-08-19 22:49 ` Richard Purdie [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=1471646993.16712.60.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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