From: Martin Sebor via Libc-alpha <libc-alpha@sourceware.org>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: tests failing on x86_64-linux (due to test-container?)
Date: Thu, 13 May 2021 15:29:58 -0600 [thread overview]
Message-ID: <1c4ea1d3-5647-9654-ccd3-06dcc7844741@gmail.com> (raw)
In-Reply-To: <xnv9863qyn.fsf@rhel8.vm>
On 4/28/21 5:54 PM, DJ Delorie wrote:
> Martin Sebor <msebor@gmail.com> writes:
>>> (which should be bind-mounted inside your test chroot, which would be
>>> /build/glibc/testroot.root/build/glibc/nss/tst-nss-test3)
>>
>> /build/glibc/testroot.root/build/glibc/ is empty.
>
> Only because you're not inside the container, where the mount exists.
> Containers are weird ;-)
>
>> error: test-container.c:235: can't mount /ssd/src/glibc onto
>> /build/glibc/testroot.root/ssd/src/glibc
>
> Sigh, you have "too many permissions" :-P Again, containers are weird.
>
> You may be able to run test-container manually, but test-container
> itself is built against the just-built glibc
>
>>> Also, selinux might be interfering.
>>
>> That doesn't sound encouraging. Anything I should look at/for?
>
> Dunno, I typically disable selinux.
I haven't been able to make that work yet but I also haven't tried
too hard. I'll keep at it.
>
> Just for paranoia's sake... does all this work on a newer Fedora?
Yes. I just installed F33 on my laptop and it works fine there.
I haven't changed my main workstation though. It was a pain to
set up.
Martin
next prev parent reply other threads:[~2021-05-13 21:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 18:17 tests failing on x86_64-linux Martin Sebor via Libc-alpha
2020-12-09 18:28 ` H.J. Lu via Libc-alpha
2020-12-09 21:17 ` Martin Sebor via Libc-alpha
2020-12-09 21:44 ` H.J. Lu via Libc-alpha
2020-12-09 22:31 ` H.J. Lu via Libc-alpha
2020-12-10 2:50 ` H.J. Lu via Libc-alpha
2020-12-15 0:55 ` Martin Sebor via Libc-alpha
2021-04-28 20:07 ` tests failing on x86_64-linux (due to test-container?) Martin Sebor via Libc-alpha
2021-04-28 20:37 ` DJ Delorie via Libc-alpha
2021-04-28 21:50 ` Martin Sebor via Libc-alpha
2021-04-28 23:08 ` DJ Delorie via Libc-alpha
2021-04-28 23:42 ` Martin Sebor via Libc-alpha
2021-04-28 23:54 ` DJ Delorie via Libc-alpha
2021-05-13 21:29 ` Martin Sebor via Libc-alpha [this message]
2022-01-12 22:04 ` Martin Sebor via Libc-alpha
2022-01-12 22:13 ` H.J. Lu via Libc-alpha
2022-01-12 23:24 ` Martin Sebor via Libc-alpha
2022-01-14 23:51 ` Martin Sebor via Libc-alpha
2022-01-17 18:04 ` Adhemerval Zanella via Libc-alpha
2022-01-17 19:09 ` Joseph Myers
2022-01-20 22:23 ` Martin Sebor via Libc-alpha
2020-12-16 10:21 ` tests failing on x86_64-linux Florian Weimer via Libc-alpha
2020-12-09 19:03 ` Florian Weimer via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c4ea1d3-5647-9654-ccd3-06dcc7844741@gmail.com \
--to=libc-alpha@sourceware.org \
--cc=dj@redhat.com \
--cc=msebor@gmail.com \
/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).