This is the mail archive of the
mailing list for the glibc project.
Re: RFC: Test hook for nss_files testing
- From: Florian Weimer <fweimer at redhat dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 11 Dec 2015 13:15:28 +0100
- Subject: Re: RFC: Test hook for nss_files testing
- Authentication-results: sourceware.org; auth=none
- References: <5664991E dot 4090105 at redhat dot com> <5665BA0A dot 50504 at redhat dot com> <5665D13C dot 1040703 at redhat dot com> <5665F130 dot 1040209 at redhat dot com> <56698F52 dot 2040008 at redhat dot com> <566A728A dot 1060903 at redhat dot com>
On 12/11/2015 07:51 AM, Carlos O'Donell wrote:
>> I'm not so sure. Setting up the chroot in a realistic way is quite
>> difficult. You need to populat /dev and /dev/pts in some way, and
>> arrange for the necessary GCC and platform bits being present, whatever
>> they are. âmake installâ may not actually produce a tree layout that is
>> used by any downstream distribution. And so on. The list of issues is
>> quite long.
> In which regard do you think this is not ideal?
It's quite a bit of work and very tightly integrated with individual
distributions. Test hooks and in-tree testing directly benefit everyone
who looks at test results.
> Should we rely on distro images?
It's not just that, you'd also need to build glibc according to the
distribution's needs, regarding file system layout and so on. So it's
really difficult to see how this can be part of the upstream testing.
> Lastly, we may have to rely on some basic building blocks for doing this kind
> of testing. Without those building blocks we mark the test UNSUPPORTED.
> It is entirely plausible that at the start the test only works on x86_64,
> requires docker, and runs slim Fedora container for testing.
But that still looks like it needs network access, which builders
generally lack (and rightly so).