Bug#953869: marked as done (glibc: Please disable nptl/tst-cond8-static and nptl/tst-mutex{,pi}8-static on sparc64)
Your message dated Wed, 25 Mar 2020 14:44:46 +0100
with message-id <20200325134446.GD2857@aurel32.net>
and subject line Re: Bug#953869: glibc: Please disable nptl/tst-cond8-static and nptl/tst-mutex{,pi}8-static on sparc64
has caused the Debian Bug report #953869,
regarding glibc: Please disable nptl/tst-cond8-static and nptl/tst-mutex{,pi}8-static on sparc64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
953869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953869
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.31-0experimental0
Severity: normal
User: debian-sparc@lists.debian.org
Usertags: sparc64
Hello!
With glibc 2.31, the number of testsuite failures has dropped to just three
failures on sparc64:
FAIL: nptl/tst-cond8-static
FAIL: nptl/tst-mutex8-static
FAIL: nptl/tst-mutexpi8-static
I have reported these failures upstream [1, 2].
Since 2.31 seems to be a big improvement on sparc64, can you disable these
three tests so that we can quickly enable 2.31 on sparc64? 2.30 seems to be
broken on sparc64, unfortunately, as it already causes segfaults during
installation:
Setting up libc6:sparc64 (2.30-2) ...
dpkg: error processing package libc6:sparc64 (--configure):
installed libc6:sparc64 package post-installation script subprocess was killed by signal (Segmentation fault)
Errors were encountered while processing:
libc6:sparc64
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt-get failed.
E: Package installation failed
Thanks,
Adrian
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=25671
> [2] https://sourceware.org/bugzilla/show_bug.cgi?id=25672
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Version: 2.30-4
On 2020-03-15 12:50, John Paul Adrian Glaubitz wrote:
> On 3/14/20 11:26 AM, John Paul Adrian Glaubitz wrote:
> > With glibc 2.31, the number of testsuite failures has dropped to just three
> > failures on sparc64:
> >
> > FAIL: nptl/tst-cond8-static
> > FAIL: nptl/tst-mutex8-static
> > FAIL: nptl/tst-mutexpi8-static
> >
> > I have reported these failures upstream [1, 2].
> >
> > Since 2.31 seems to be a big improvement on sparc64, can you disable these
> > three tests so that we can quickly enable 2.31 on sparc64?
>
> I have rebuild glibc_2.31 with these tests marked as XFAIL multiple times
> and the number of failures is reproducible for me.
>
> So, can we get this change included?
>
This has been done in version 2.30-4, but I forgot to close the bug in
the changelog. Closing it now.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
--- End Message ---
Reply to: