This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Running the tests
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Ryan Arnold" <ryan dot arnold at gmail dot com>
- Cc: "Reuben Thomas" <rrt at sc3d dot org>, libc-help at sourceware dot org
- Date: Tue, 13 May 2008 09:39:16 -0400
- Subject: Re: Running the tests
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=1PRa+U4g81bwf1Efg1+MVS/e1NnEDnKhk0jjz9qso40=; b=QS7Tvz9w75Mi1RGef4FEKxTEsPUjNX3X48xDOdw3YLLTwf6XQreBzPy0XD8uJguL/bB6R5ZIhwqmf9mMaFt7uTj5fHgibXsOdc8nNTiSKNt9HguDRW0ZpUgpI+689GBqWCrfpsZpJVYlf7nj2bX81sqyql4wPuN2Tw2hhqgwxz8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=CznAd2wT5tlwAoXJESpBGVHINCvq0UBhsfhI8Diog9Mqw3/KiuOh/mwc6mDXXzaX/Dn9Bfs+7G675oDqzgEgYB/qoUYQmiHOyBoU5qbQl/f3grQEgkxszNpRS5e9DqlTXT1o2Peh6J39oGB5YKYpk/xWDwjAO0zLladvG/3hzIc=
- References: <alpine.DEB.1.00.0805031346060.10349@canta> <200805031923.13241.vapier@gentoo.org> <alpine.DEB.1.00.0805040054250.10349@canta> <200805032050.19493.vapier@gentoo.org> <alpine.DEB.1.00.0805122311040.10349@canta> <ff4da150805121616i4cf70647x455d18d7eb18de90@mail.gmail.com>
On Mon, May 12, 2008 at 7:16 PM, Ryan Arnold <ryan.arnold@gmail.com> wrote:
> On Mon, May 12, 2008 at 5:23 PM, Reuben Thomas <rrt@sc3d.org> wrote:
> > I'm building glibc from CVS and getting test failures. Each time I run "make
> > check" it seems to carry on from the last failure; is there a way to stop
> > this so I can repeatedly run the last failing test and try to see what the
> > problem is?
>
> Rueben,
>
> What I usually do is copy the output of the make check fragment that
> failed out into a shell script and then execute that as many times as
> I need.
>
> I think you may also be able to remove the test .o files.
Remove the '*.out' file associated with the test and a "make check"
will rerun that test and then continue onward. For example the
tst-vfork test creates a tst-vfork.out result file.
I don't recommend that though, I recommend running "make -k check >
check.log", reviewing *all* the test results. Find the command in
check.log that ran the failing test and as Ryan says, run it over and
over to do the debugging. The command will take the form of
"/path/to/new/ld.so --library-path /paths/to/new/libs test-binary."
Cheers,
Carlos.