public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/29575] [Regression 2.34/2.25]: Large number of testsuite failures on sparc*-linux-*-* Date: Fri, 16 Sep 2022 11:43:34 +0000 [thread overview] Message-ID: <bug-29575-131-TPP20CtycL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29575-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29575 Carlos O'Donell <carlos at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2022-09-16 Ever confirmed|0 |1 --- Comment #1 from Carlos O'Donell <carlos at redhat dot com> --- (In reply to John Paul Adrian Glaubitz from comment #0) > The testsuite currently fails with so many failed tests on Debian unstable > on sparc64 that I assume there is some underlying issue on SPARC that needs > to be addressed: Please reach out to the debian-glibc team discuss these issues. The distro team is best placed to understand the test results of Debian's glibc given the context of the previous build results. > Full build log: > https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=sparc64&ver=2.35- > 0experimental3&stamp=1662895877&raw=0 There were no distribution or machine maintainers that did any testing for sparc64 in glibc 2.36: https://sourceware.org/glibc/wiki/Release/2.36#SPARC_.2864-bit.29 I'd say the sparc64 support is at risk of being removed if maintainers and developers are not testing or supporting the architecture. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-16 11:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-16 8:44 [Bug build/29575] New: " glaubitz at physik dot fu-berlin.de 2022-09-16 11:43 ` carlos at redhat dot com [this message] 2022-09-30 8:53 ` [Bug build/29575] " glaubitz at physik dot fu-berlin.de 2022-09-30 8:53 ` [Bug build/29575] [Regression 2.34/2.25]: Many testsuite failures when not building with "--disable-default-pie" on sparc*-linux-* glaubitz at physik dot fu-berlin.de 2022-09-30 8:54 ` [Bug build/29575] [2.35/2.36]: " glaubitz at physik dot fu-berlin.de 2022-10-04 17:32 ` adhemerval.zanella at linaro dot org 2022-11-06 15:08 ` glaubitz at physik dot fu-berlin.de 2022-11-07 6:54 ` sam at gentoo dot org 2022-11-12 23:44 ` glaubitz at physik dot fu-berlin.de 2023-07-19 11:48 ` glaubitz at physik dot fu-berlin.de 2023-07-19 12:46 ` adhemerval.zanella at linaro 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-29575-131-TPP20CtycL@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: linkBe 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).