This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Linux Foundation Collaboration Summit: The future of The GNU CLibrary.
From: "Joseph S. Myers" <joseph@codesourcery.com>
Date: Wed, 28 Mar 2012 09:13:42 +0000 (UTC)
> On Tue, 27 Mar 2012, Jeff Law wrote:
>
>> On 03/27/2012 09:23 PM, Siddhesh Poyarekar wrote:
>> > On Wed, Mar 28, 2012 at 8:33 AM, Carlos O'Donell
>> > <carlos@systemhalted.org> wrote:
>> > > Anything goes, I'm looking to create a grab-bag of ideas from the
>> > > community including such crazy things as:
>> > >
>> >
>> > How about a dejagnu (or equivalent) testsuite? If dejagnu is ok, I can
>> > work on porting the current test cases into something similar to
>> > gcc/gdb.
>> dejagnu is dreadful; there's got to be a better designed & implemented testing
>> harness we can use. Improving testing would be a big step forward, but not
>> with dejagnu, please.
>
> DejaGnu, properly used, brings you remote-target, remote-host and
> installed-toolchain testing for free. Remote-host (running compilers
> remotely) isn't particularly interesting for glibc, but the others are -
> although remote-target cases for glibc are very limited (testing on a
> Unix-like system over SSH) which simplifies supporting things in different
> systems.
Another minus of dejagnu is that it's hard to parallelize. GCC gets
around this by running the tests in groups, but it's extremely ugly.
And parallelization is one of the main limitations I keep running into
when trying to validate glibc changes. I have 128 cpus and they are
hardly used.