From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: eglibc testing?
Date: Thu, 16 Jun 2011 11:15:30 +0100 [thread overview]
Message-ID: <1308219330.25285.4194.camel@phil-desktop> (raw)
I just ran "make check" under qemu on my eglibc-2.13 build (from oe-core
master) and got rather a lot of failures. It wasn't immediately obvious
to me whether these were libc bugs, qemu infelicities, oe-related
harness problems, or some kind of local finger trouble.
Before I spend too much time investigating this, are other people seeing
the same effect? What approach do the Yocto folks use for glibc
testing: are they running the testsuite directly on target hardware, or
via qemu, or something else?
The gcc testsuite is next on my list to look at and, again, I'd be
interested to hear what approach other folks are using there and what
sort of results they are currently getting.
thanks
p.
next reply other threads:[~2011-06-16 10:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 10:15 Phil Blundell [this message]
2011-06-16 13:41 ` eglibc testing? Khem Raj
2011-06-16 14:29 ` Phil Blundell
2011-06-16 23:18 ` Khem Raj
2011-06-17 10:13 ` Phil Blundell
2011-06-17 10:25 ` Richard Purdie
2011-06-17 10:41 ` Phil Blundell
2011-06-30 10:32 ` Phil Blundell
2011-06-30 14:29 ` Khem Raj
2011-08-04 9:24 ` Phil Blundell
2011-08-04 15:10 ` Khem Raj
2011-12-09 6:25 ` Khem Raj
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=1308219330.25285.4194.camel@phil-desktop \
--to=pb@pbcl.net \
--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