Re: [GNU Autoconf 2.69.129-0263a] testsuite: 140 210 212 failed

[Antti Nuortimo]

On Mon, Oct 6, 2014 at 9:00 PM, Eric Blake <address@hidden> wrote:

> On 10/06/2014 03:54 AM, Antti Nuortimo wrote:
> > Hi,
> >
> > the testsuite.log with fails as an attachment.
> >
> > ## ------------- ##
> > ## Test results. ##
> > ## ------------- ##
> >
> > ERROR: 320 tests were run,
> > 7 failed (4 expected failures).
> > 189 tests were skipped.
> >
> > Running Debian GNU/Linux Wheezy on x86-64, custom kernel 3.17-rc7,
> recently
> > compiled and installed binutils 2.17 in /usr/local (if that matters).
> >
>
> >  140: autotest.at:385    Syntax error
> >       autotest
> >  210: autotest.at:1495   parallel syntax error
> >       autotest
> >  212: autotest.at:1530   parallel autotest and signal handling
> >       autotest
>
> Thanks for the report.
>

You're welcome.


> > ./micro-suite: 12:
> /home/antti/koodi/autoconf/tests/testsuite.dir/140/micro-suite.dir/at-groups/2/test-source:
> Syntax error: ")" unexpected
> > stdout:
> > ## --------------------------------------------------- ##
> > ## GNU Nonsense 1.0 test suite: artificial test suite. ##
> > ## --------------------------------------------------- ##
> >   1: my only test                                    ok
> >   2: syntax                                         ./autotest.at:385:
> exit code was 2, expected 1
>
> > 140. autotest.at:385: 140. Syntax error (autotest.at:385): FAILED (
> autotest.at:385)
>
> Looks like your shell gave a different failure status than the testsuite
> expected, and that in this case the testsuite should be updated to
> tolerate all non-zero status as okay.  What shell are you using?
>

bash version 4.2.37(1)-release, shipped with Debian Wheezy, from an
official Debian repo.

$ bash --version
prints the following:

GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

$

>
> > #                             -*- compilation -*-
> > 210. autotest.at:1495: testing parallel syntax error ...
>
> I'm guessing this one is similar
>
> > All 2 tests were successful.
> > ./autotest.at:1495: ${CONFIG_SHELL-$SHELL} -c 'case `. ./syntax; echo
> $?` in
> >                 0|"") exit 77;;
> >               esac'
> > stderr:
> > ./syntax: line 2: syntax error: unexpected end of file
> > stdout:
> > ./autotest.at:1495: $CONFIG_SHELL ./micro-suite -j
> > stderr:
> > ./micro-suite: 12:
> /home/antti/koodi/autoconf/tests/testsuite.dir/210/micro-suite.dir/at-groups/2/test-source:
> Syntax error: ")" unexpected
> > stdout:
> > ## --------------------------------------------------- ##
> > ## GNU Nonsense 1.0 test suite: artificial test suite. ##
> > ## --------------------------------------------------- ##
> >
> >   1: my only test                                    ok
> >   3: another test                                    ok
> >
> > ## ------------- ##
> > ## Test results. ##
> > ## ------------- ##
> >
> > All 2 tests were successful.
> > ./autotest.at:1495: exit code was 0, expected 1
>
> Hmm.  In this case, the syntax error definitely showed up on stderr, but
> your shell kept going with a 0 exit status.  That feels more like a bug
> in your shell, maybe?
>

A bug is the shell is of course possible. My bash is from Debian Wheezy
official repo.


>
> > #                             -*- compilation -*-
> > 212. autotest.at:1530: testing parallel autotest and signal handling ...
> > ./autotest.at:1532: mkfifo fifo || exit 77
>
> > ./micro-suite: 9:
> /home/antti/koodi/autoconf/tests/testsuite.dir/212/micro-suite.dir/at-groups/4/test-source:
> Syntax error: EOF in backquote substitution
> > stdout:
> > ## -------------------------------------------------------------- ##
> > ## GNU Nonsense 1.0 test suite: suite to test parallel execution. ##
> > ## -------------------------------------------------------------- ##
> >   1: test number 1                                   ok
> >   2: test number 2                                   ok
> >   3: test number 3                                   ok
> >   4: killer test                                    ./autotest.at:1584:
> exit code was 2, expected 130
>
> I know that upstream dash has been doing some patches lately to try and
> improve exit status after particular corner cases; could it be the case
> that you are trying a relatively new dash build where one of these
> patches may be buggy?


I'm using bash and started autoconf from bash, but in the case autoconf
would execute dash, I do have dash also installed, so autoconf can execute
it if needed. My dash version is 0.5.7-3 (shipped with Debian Wheezy, from
an official Debian repo).

Best regards,

Antti Nuortimo



> --
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
>