[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Autoconf 2.59] testsuite: 69 71 136 146 162 failed
From: |
Paul Eggert |
Subject: |
Re: [GNU Autoconf 2.59] testsuite: 69 71 136 146 162 failed |
Date: |
Mon, 06 Sep 2004 14:36:08 -0700 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
Michael Eisenstein <address@hidden> writes:
> This left me asking the question why do these two tests expect there
> to be an extra copy of testsuite.log while test 132 AC_PROG_RANLIB
> expects the opposite?
expout is created by the same procedure that creates at-stdout, namely
ls -1 | sed '/^at-/d;/^state-/d;/^config\./d' | sort
If this procedure is buggy at times for some reason, then it's not
surprising that an extra testsuite.dir will occur sometimes in expout,
and sometimes in at-stdout.
> From what I understand ./testsuite -v -d 136 is instructing the
> testsuite to only run that test in a directory correct?
Yes.
> Based on this I ran each of the tests reporting failure in a
> similiar manner and they reported success. these tests were 132,
> 145, 148, 153. And yes when I reran the entire test suite test 136
> was not failing.
Sigh. It's a common problem: turn on debugging and the problem goes away.
> Would it be worthwhile to start from scratch and send you the console
> outputs from the entire process?
I'd rather try a different way to debug. What happens if you run
"ktrace -f trfile -i make check"? Assuming that "make check" fails in
the same way, can you look for the trace of the "ls + sed + sort"
command that output testsuite.log twice, to see whether it is "ls", or
"sed", or "sort" that is buggy?