Chroot testsuite

[Ryan Arnold]

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