From: Mark Wielaard <mark@klomp.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: libc-alpha@sourceware.org
Subject: Re: state of the ports
Date: Sun, 25 Feb 2024 23:47:42 +0100 [thread overview]
Message-ID: <20240225224742.GB15517@gnu.wildebeest.org> (raw)
In-Reply-To: <4155299.iIbC2pHGDl@noumea>
Hi,
On Fri, Feb 02, 2024 at 03:35:04AM +0100, Andreas K. Huettel wrote:
> So... after all the testing gone into the release I thought I'd
> summarize a bit for the list here - by sorting the glibc ports into
> "excellent", "good", "medium", "bad", and "nobody even tried".
We have several buildbots at builder.sourceware.org for glibc which
probably should start sending build failure emails when things break.
https://builder.sourceware.org/buildbot/#/builders?tags=glibc
> 1. EXCELLENT
> ============
>
> aarch64
> - tests pass nearly everywhere
> - on raspi, likely timeouts
https://builder.sourceware.org/buildbot/#/builders/glibc-debian-arm64
Used to have some tests time out, but since we are running with
TIMEOUTFACTOR=4 is all green:
4807 PASS
22 UNSUPPORTED
16 XFAIL
2 XPASS
> powerpc64
> powerpc64le
> - tests pass
https://builder.sourceware.org/buildbot/#/builders/glibc-debian-ppc64
https://builder.sourceware.org/buildbot/#/builders/glibc-fedora-ppc64le
We only do a make subdirs=elf check but those all pass:
glibc-debian-ppc64:
341 PASS
5 UNSUPPORTED
2 XPASS
glibc-fedora-ppc64le:
338 PASS
2 UNSUPPORTED
2 XPASS
> s390x
> - tests pass
https://builder.sourceware.org/buildbot/#/builders/glibc-fedora-s390x
Likewise, just subdirs=elf:
336 PASS
2 UNSUPPORTED
2 XPASS
For ppc64, ppc64le and s390x we could run a different subset if that
is more useful. The issue really is the nptl subdir, which just takes
a very long time (because it doesn't run any test in parallel?)
> x86-64
> - tests pass
Fully green on glibc-fedora-x86_64
https://builder.sourceware.org/buildbot/#/builders/glibc-fedora-x86_64
4945 PASS
274 UNSUPPORTED
16 XFAIL
4 XPASS
But on glibc-debian-testing-x86_64 and glibc-rawhide-x86_64 it
occassionally sees one FAIL: elf/tst-audit10 which times out even with
TIMEOUTFACTOR=4
> riscv64
> - ~5 failures, but there may be timeouts among them
https://builder.sourceware.org/buildbot/#/builders/glibc-ubuntu-riscv
With TIMEOUTFACTOR=4 there are no (timeout) failures anymore.
4699 PASS
24 UNSUPPORTED
16 XFAIL
2 XPASS
This is the slowest of them all (takes 2 hours 15 minutes to 3 hours,
depending on how good the ccache is). But we have multiple riscv
boards now thanks to StarFive and one of them is dedicated to glibc.
> sparc
> - ~5 failures (!)
Seeing even more failures:
9 FAIL
4725 PASS
23 UNSUPPORTED
17 XFAIL
2 XPASS
FAIL: elf/tst-audit18
FAIL: elf/tst-pldd
FAIL: elf/tst-ptrguard1
FAIL: math/test-float64x-float128-mul
FAIL: nptl/tst-mutex9
FAIL: nptl/tst-oddstacklimit
FAIL: posix/tst-spawn7-pidfd
FAIL: socket/tst-socket-timestamp
FAIL: stdlib/tst-setcontext2
> x86 (32bit)
> - in general tests pass
> - there may be breakage on old hw (pentium2)
Really a i386 VM on x86_64:
https://builder.sourceware.org/buildbot/#/builders/glibc-debian-i386
4851 PASS
40 UNSUPPORTED
16 XFAIL
6 XPASS
Cheers,
Mark
next prev parent reply other threads:[~2024-02-25 22:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 2:35 Andreas K. Huettel
2024-02-02 7:51 ` Xi Ruoyao
2024-02-02 7:53 ` Xi Ruoyao
2024-02-02 11:28 ` Florian Weimer
2024-02-02 21:40 ` Andreas K. Huettel
2024-02-22 17:11 ` Xi Ruoyao
2024-02-22 20:30 ` Andreas K. Huettel
2024-02-04 7:37 ` Stafford Horne
2024-02-04 11:40 ` Andreas K. Huettel
2024-02-25 22:47 ` Mark Wielaard [this message]
2024-02-26 12:44 ` Adhemerval Zanella Netto
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=20240225224742.GB15517@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).