From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: Steve Sakoman <steve@sakoman.com>,
Ross Burton <ross.burton@arm.com>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
Randy MacLeod <randy.macleod@windriver.com>,
"Kokkonda, Sundeep" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] Toolchain test results
Date: Thu, 20 Jul 2023 12:26:52 +0100 [thread overview]
Message-ID: <1c22b4fdfdcf22b58f7e06df872a9e0980645328.camel@linuxfoundation.org> (raw)
In-Reply-To: <1772EB68FCA90E64.1400@lists.openembedded.org>
On Tue, 2023-07-18 at 10:14 +0100, Richard Purdie via
lists.openembedded.org wrote:
> qemuarm has ~350 failures
> qemuarm64 has ~350 failures
> qemux86-64 has ~4000 (3900 in glibc)
> qemux86 has ~4000 (3500 in glibc)
> qemuppc has ~600 failures
> qemumips64 has ~5000 failures (all over)
> qemumips has ~1600 failures
>
> Anuj: Can Intel look into the glibc test failures on x86?
I realised the glibc issues were due to the network being disabled for
the tests and have sent a patch to fix that. That reduces the failures
from ~3900 to ~330. We should really try and reduce that further but it
is a start!
Cheers,
Richard
next parent reply other threads:[~2023-07-20 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1772EB68FCA90E64.1400@lists.openembedded.org>
2023-07-20 11:26 ` Richard Purdie [this message]
2023-07-26 6:00 ` [OE-core] Toolchain test results Mittal, Anuj
2023-07-26 6:29 ` Khem Raj
2023-07-26 6:45 ` Mittal, Anuj
[not found] ` <177557ED3E322BBA.21334@lists.openembedded.org>
2023-07-27 6:05 ` Mittal, Anuj
2023-07-26 9:17 ` Richard Purdie
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=1c22b4fdfdcf22b58f7e06df872a9e0980645328.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=ross.burton@arm.com \
--cc=steve@sakoman.com \
/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