public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nss/27537] [2.33 Regression] FAIL: nss/tst-reload2
Date: Mon, 08 Mar 2021 13:34:20 +0000 [thread overview]
Message-ID: <bug-27537-131-PK79eIQdRw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27537-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27537
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
This is definitely odd. The test failures I've seen where on hosts where there
were no IPv6 notworking interfaces.
Maybe propagating IPv6 support into the container fails for some reason? But
then support/test-container.c does not actually enter a network namespace, so
this shouldn't be a problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-08 13:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 17:45 [Bug nss/27537] New: " hjl.tools at gmail dot com
2021-03-08 8:08 ` [Bug nss/27537] " fweimer at redhat dot com
2021-03-08 13:11 ` hjl.tools at gmail dot com
2021-03-08 13:34 ` fweimer at redhat dot com [this message]
2021-03-08 15:15 ` hjl.tools at gmail dot com
2021-03-08 16:17 ` skpgkp2 at gmail dot com
2021-03-08 17:39 ` skpgkp2 at gmail dot com
2021-03-08 17:57 ` schwab@linux-m68k.org
2021-03-09 19:08 ` [Bug nss/27537] [2.33/2.34 " hjl.tools at gmail dot com
2021-03-09 20:09 ` dj at redhat dot com
2021-03-09 21:06 ` hjl.tools at gmail dot com
2021-03-10 14:38 ` hjl.tools at gmail dot com
2021-03-11 8:25 ` stli at linux dot ibm.com
2021-03-11 22:08 ` dj 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-27537-131-PK79eIQdRw@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).