From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "steve@sakoman.com" <steve@sakoman.com>,
"ross.burton@arm.com" <ross.burton@arm.com>,
"randy.macleod@windriver.com" <randy.macleod@windriver.com>,
"Sundeep.Kokkonda@windriver.com" <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] Toolchain test results
Date: Wed, 26 Jul 2023 06:00:42 +0000 [thread overview]
Message-ID: <e6b6426580c3f6be5f492e2d1b9ae2a0b8049d12.camel@intel.com> (raw)
In-Reply-To: <1c22b4fdfdcf22b58f7e06df872a9e0980645328.camel@linuxfoundation.org>
On Thu, 2023-07-20 at 12:26 +0100, Richard Purdie wrote:
> 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!
>
A lot of locale/iconv tests seemed to be failing when calling write
with large buffers/files over NFS. Some of others were triggering OOM.
I ran the tests again after making a few changes:
https://autobuilder.yocto.io/pub/non-release/20230726-11/testresults/qemux86-64-tc/
After switching NFS mount to TCP and increasing the memory available to
1024, the number of tests failed came down to 69.
=======================================================================
=======================================
qemux86-64 PTest Result Summary
=======================================================================
=======================================
-----------------------------------------------------------------------
---------------------------------------
Recipe | Passed | Failed | Skipped | Time(s)
-----------------------------------------------------------------------
---------------------------------------
binutils | 289 | 0 | 8 | -
binutils-gas | 1582 | 4 | 1 | -
binutils-ld | 1622 | 6 | 111 | -
gcc | 149696 | 28 | 27599 | -
gcc-g++ | 219260 | 30 | 21108 | -
gcc-libatomic | 27 | 1 | 27 | -
gcc-libgomp | 3426 | 1 | 1962 | -
gcc-libitm | 24 | 1 | 24 | -
gcc-libstdc++-v3 | 9695 | 32 | 5459 | -
glibc | 4984 | 69 | 147 | -
rust | 15768 | 0 | 554 | -
-----------------------------------------------------------------------
---------------------------------------
Thanks,
Anuj
next prev parent reply other threads:[~2023-07-26 6:00 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 ` [OE-core] Toolchain test results Richard Purdie
2023-07-26 6:00 ` Mittal, Anuj [this message]
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=e6b6426580c3f6be5f492e2d1b9ae2a0b8049d12.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--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