public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug ports/25672] New: nptl/tst-mutex8-static and nptl/tst-mutexpi8-static failing on sparc64 on Linux
Date: Sat, 14 Mar 2020 08:55:59 +0000 [thread overview]
Message-ID: <bug-25672-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25672
Bug ID: 25672
Summary: nptl/tst-mutex8-static and nptl/tst-mutexpi8-static
failing on sparc64 on Linux
Product: glibc
Version: 2.31
URL: https://buildd.debian.org/status/fetch.php?pkg=glibc&a
rch=sparc64&ver=2.31-0experimental0&stamp=1584003885&r
aw=0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ports
Assignee: unassigned at sourceware dot org
Reporter: glaubitz at physik dot fu-berlin.de
CC: adhemerval.zanella at linaro dot org, carlos at redhat dot com,
jrtc27 at jrtc27 dot com, matorola at gmail dot com
Target Milestone: ---
Target: sparc*-*-*
With 2.31, the number of testsuite failures on Linux/sparc64 has dropped
dramatically to just three failures. One of the failures left is
nptl/tst-mutex8-static and nptl/tst-mutexpi8-static, for a full log see:
https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.31-0experimental0&stamp=1584003885&raw=0
Are these failures which can be safely ignored or do they indicate a larger
problem?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-03-14 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 8:55 glaubitz at physik dot fu-berlin.de [this message]
2020-03-17 13:07 ` [Bug ports/25672] " adhemerval.zanella at linaro dot org
2020-03-17 15:40 ` aurelien at aurel32 dot net
2024-01-17 13:21 ` adhemerval.zanella at linaro dot org
2024-01-18 4:59 ` sam at gentoo dot org
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=bug-25672-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).