Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Björn Stenberg" <bjst@enea.com>
Cc: 'Patches and discussions about the oe-core layer'
	<openembedded-core@lists.openembedded.org>
Subject: ptest results
Date: Tue, 09 Apr 2013 23:45:19 -0700	[thread overview]
Message-ID: <51650A7F.2020904@linux.intel.com> (raw)


Bjorn:

I ran ptest-runner finally I saw that there were failures, I am 
wondering if these are expected?

http://pastebin.com/PAH3gJT0

The bash packages did not seem to get split out correct, the ptest seem 
to land in ${PN} not in ${PN}-ptest, you might want to look into this also.

With your patch, the ptest related debug files did go into the 
${PN}-dbg, is this what you intend or should they go into a 
${PN}-ptest-dbg package?

Thanks


-- 
     Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System




             reply	other threads:[~2013-04-10  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  6:45 Saul Wold [this message]
2013-04-10 13:27 ` ptest results Björn Stenberg
2013-04-11  9:14   ` Björn Stenberg

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=51650A7F.2020904@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=bjst@enea.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