From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: eglibc testing?
Date: Fri, 9 Dec 2011 06:25:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20111209T072203-634@post.gmane.org> (raw)
In-Reply-To: 1308219330.25285.4194.camel@phil-desktop
Phil Blundell <pb@...> writes:
>
> 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.
>
Hi Phil
I have finally found some time to cobble up howto cross test eglibc
on top of oe-core
I have tried to document it here
http://sakrah.homelinux.org/blog/2011/12/cross-testing-eglibc-regression-
testsuite-using-openembedded-coreqemu/
Right now I see around 34 failures on arm out of 1100 odd tests it ran
Let me know if you have any feedback on it.
I will also post the cross gcc testing howto sometimes soon
> thanks
>
> p.
>
prev parent reply other threads:[~2011-12-09 6:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 10:15 eglibc testing? Phil Blundell
2011-06-16 13:41 ` 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 [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=loom.20111209T072203-634@post.gmane.org \
--to=raj.khem@gmail.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