On Friday 22 July 2011, Jim Meyering wrote:
> Stefano Lattarini wrote:
> > Hi Jim, thanks for the report.
> 
> Hi Stefano,
> 
> Thanks for the quick response.
> 
> >> I built the latest and ran "make check TESTSUITEFLAGS=-j20" on Fedora 15.
> >>
> > Note that the `TESTSUITEFLAGS' variable has no effect on Automake-generated
> > testsuite harness.  What you probably wanted was simply "make check -j20".
> ...
> >
> > A fix for these failures (which I've only encountered when running the
> > automake testsuite with Linux -> MinGW cross compilers) should have
> > been applied to the testsuite-work branch some time ago (see commit
> > `v1.11-871-geb147a1', "lex tests: avoid spurious failures when LEXLIB
> > isn't found").
> 
> Good!  Will this fix make it to "master" soon?
>
I don't really know; the idea is to eventually merge 'testsuite-work' into
'master', but Ralf wants to take a look at its (many) commits before doing
the merge (and I agree with him that such a review would be useful).

In the meantime, when you want to test the "bleeding-edge" automake, I
suggest that you use 'testsuite-work' instead of 'master' (notice that
the latter branch is routinely merged into the former one, so you aren't
going to loose coverage).

> >> FAIL: txinfo21.test (exit: 1)
> >> =============================
> ...
> >> + test -d rec/main3.html
> >> + is_newest main.html main.texi
> >> ++ find main.html main.texi -newer main.html
> >> + is_newest_files=main.html/index.html
> >> + test -z main.html/index.html
> >> + exit_status=1
> >> + set +e
> >> + cd /h/j/w/co/automake/tests
> >> + case $exit_status,$keep_testdirs in
> >> + test 0 '!=' 0
> >> + echo 'txinfo21: exit 1'
> >> txinfo21: exit 1
> >> + exit 1
> >>
> > Ah, a failure I've introduced in 'maint' with commit `v1.11-360-ga370e2f'
> > "tests: fix spurious failure of txinfo21.test on FreeBSD".  It is due
> > to a limitation of the `is_newest' subroutine I hadn't thought about
> > (i.e., it doesn't work as expected on directories).  Should we hack
> > around this, or try to fix the `is_newest' subroutine instead?  I think
> > fixing `is_newest' is the best route. Anyway, I'll be AFK until tomorrow,
> > but then I'll give it a try (unless someone wants to beat me ;-)
> 
> I can wait ;-)
> Thanks.
>
Fixed by the attached patch (tested with GNU find and Solaris find).
I will allow a day or so for comments before pushing.

> A quick note about quoting: when there are hundreds of lines of
> quoted text, and you insert a couple groups of 5-6 lines, it's
> good to remove as much of that context as possible, if only
> so that those trying to read your reply will not accidentally
> skip over some part of it (I nearly did just that).
> 
Noted (BTW, I had deleted most of the log text you had originally
posted, but I can see that I had indeed still kept too much irrelevant
context).

Thanks,
  Stefano