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/31892] Always install mtrace. Date: Thu, 13 Jun 2024 19:06:02 +0000 [thread overview] Message-ID: <bug-31892-131-RcSCzElhrn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31892-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31892 --- Comment #2 from Carlos O'Donell <carlos at redhat dot com> --- The following tests are incorrectly conditionalized: FAIL: misc/tst-allocate_once-mem FAIL: misc/tst-error1-mem FAIL: nptl/tst-stack3-mem FAIL: posix/bug-ga2-mem FAIL: posix/bug-glob2-mem FAIL: posix/bug-regex14-mem FAIL: posix/bug-regex2-mem FAIL: posix/bug-regex21-mem FAIL: posix/bug-regex31-mem FAIL: posix/bug-regex36-mem FAIL: posix/tst-boost-mem FAIL: posix/tst-fnmatch-mem FAIL: posix/tst-glob-tilde-mem FAIL: posix/tst-pcre-mem FAIL: posix/tst-rxspencer-no-utf8-mem FAIL: posix/tst-vfork3-mem FAIL: stdio-common/tst-printf-bz18872-mem FAIL: stdio-common/tst-printf-bz25691-mem FAIL: stdio-common/tst-printf-fp-free-mem FAIL: stdio-common/tst-printf-fp-leak-mem FAIL: stdio-common/tst-vfprintf-width-prec-mem -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-13 19:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-13 17:17 [Bug build/31892] New: " carlos at redhat dot com 2024-06-13 18:44 ` [Bug build/31892] " jsm28 at gcc dot gnu.org 2024-06-13 19:06 ` carlos at redhat dot com [this message] 2024-06-14 10:09 ` fweimer at redhat dot com 2024-06-14 16:02 ` carlos at redhat dot com 2024-06-14 16:03 ` carlos at redhat dot com 2024-06-14 16:14 ` fweimer at redhat dot com 2024-06-20 8:33 ` fweimer at redhat dot com 2024-06-20 9:18 ` schwab@linux-m68k.org 2024-06-21 11:15 ` fweimer at redhat dot com
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-31892-131-RcSCzElhrn@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).