This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Chroot testsuite
- From: Ryan Arnold <ryan dot arnold at linaro dot org>
- To: OndÅej BÃlka <neleai at seznam dot cz>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, "Carlos O'Donell" <carlos at redhat dot com>, Will Newton <will dot newton at linaro dot org>, GNU C Library <libc-alpha at sourceware dot org>, Robert Savoye <rob dot savoye at linaro dot org>, Matthew Gretton-Dann <matthew dot gretton-dann at linaro dot org>
- Date: Thu, 16 Jan 2014 11:06:06 -0600
- Subject: Re: Chroot testsuite
- Authentication-results: sourceware.org; auth=none
- References: <52A764F3 dot 60501 at redhat dot com> <CAJE4xBMs-Qz4J01Z7M4ebwA11MZ_Uf6vdbSJ-GyCuZHbWNCFjw at mail dot gmail dot com> <52B3C775 dot 4070503 at redhat dot com> <CAJE4xBOBfyPsXpW9JMmDd7D2uS-BkJ019+Lsrsxu0Ydg+XvVvw at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401110109210 dot 16742 at digraph dot polyomino dot org dot uk> <CAJE4xBNKPXPhSWkCGsHm3j=k8pHDE+rjN-tjv82r3fX9WmH8gw at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401120030510 dot 11301 at digraph dot polyomino dot org dot uk> <CAJE4xBPbDrKiGUmQ+pGtM+msdwc8OMJH0WLD2zREbZ=i_qko2w at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1401140201400 dot 29865 at digraph dot polyomino dot org dot uk> <CAJE4xBNw0v94GXwFf=+6CJP2oK=NqO5hWi4ZYzP3za73DDGQMA at mail dot gmail dot com> <20140116010144 dot GB16804 at domone dot podge>
On Wed, Jan 15, 2014 at 7:01 PM, OndÅej BÃlka <neleai@seznam.cz> wrote:
> On Wed, Jan 15, 2014 at 06:22:40PM -0600, Ryan Arnold wrote:
>> I'm very interested in those sorts of tests. If glibc isn't the
>> appropriate place for them I'll create them a framework that's more
>> closely related to my build environment, but they probably won't be
>> nearly as portable.
>>
> How big should chroot be? A closest you can get to real usage is by
> running real programs. One alternative for integration tests would be use
> phoronix test suite, a downside would be that you need to install lot of
> dependencies.
The size of the chroot depends on the dependencies. For tests that
simply test execution paths through the dynamic-linker that wouldn't
otherwise be tested with other tests, the dependencies are minimal.
If you want to run the Ruby test-suite (for instance) against this
chrooted glibc install the dependency list balloons.
Personally I prefer to create chroot images using existing OS
distribution tools (like debootstrap and yum --installroot).
I think targeted integration tests that we write ourselves would be
more useful than incorporating an existing test-suite, unless that
test-suite explicitly exercises the glibc install in a way that the
package it is there to test uses glibc (for example ruby).
Ryan