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 libc/31129] New: elf/tst-stackguard1-static and ntpl/tst-stackguard1-static failing on sparc64-linux-gnu
Date: Sat, 09 Dec 2023 21:43:59 +0000 [thread overview]
Message-ID: <bug-31129-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31129
Bug ID: 31129
Summary: elf/tst-stackguard1-static and
ntpl/tst-stackguard1-static failing on
sparc64-linux-gnu
Product: glibc
Version: 2.38
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: glaubitz at physik dot fu-berlin.de
CC: adhemerval.zanella at linaro dot org, drepper.fsp at gmail dot com,
matorola at gmail dot com, sam at gentoo dot org
Target Milestone: ---
Target: sparc64-linux-gnu
On Debian unstable on sparc64 (sparc64-linux-gnu), the following two tests are
failing:
FAIL: elf/tst-stackguard1-static
FAIL: nptl/tst-stackguard1-static
Full build log in [1].
For 2.37, the two failures don't show but I'm not sure whether these are
actually simply not tested for 2.37 [2].
> [1] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.38-4&stamp=1701668542&raw=0
> [2] https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.37-13&stamp=1701640851&raw=0
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-12-09 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 21:43 glaubitz at physik dot fu-berlin.de [this message]
2024-01-17 12:48 ` [Bug libc/31129] " adhemerval.zanella at linaro dot org
2024-02-21 11:39 ` glaubitz at physik dot fu-berlin.de
2024-02-21 19:14 ` adhemerval.zanella at linaro dot org
2024-02-22 15:12 ` glaubitz at physik dot fu-berlin.de
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-31129-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).