[GNU Autoconf 2.69] testsuite: 38 501 503 failed

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GNU Autoconf 2.69] testsuite: 38 501 503 failed

Dennis Clarke-2
Yet another here but from Debian Linux 9 on AMD64 server.

See attached file with all manner of goodness therein

Dennis


autoconf-2.69_Linux_4.8.0-2-amd64_testfail_38_501_503.tar.gz (37K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [GNU Autoconf 2.69] testsuite: 38 501 503 failed

Václav Haisman-2
On 7 June 2017 at 21:02, Dennis Clarke <[hidden email]> wrote:
> Yet another here but from Debian Linux 9 on AMD64 server.
>
> See attached file with all manner of goodness therein
>
> Dennis
>

Test 38 failure appears to be a Perl change caused again:

    +do " tmp dir with  funny ' $x & #! name /ahZ8rb4B/traces.pl"
failed, '.' is no longer in @INC; did you mean do "./ tmp dir with
funny ' $x & #! name /ahZ8rb4B/traces.pl"? at
/usr/local/build/autoconf-2.69_Linux_4.8.0-2-amd64.001/bin/autoheader
line 186.
    +autoheader: error: AC_CONFIG_HEADERS not found in  file with
funny ' $x & #! name .in
./tools.at:1310: exit code was 1, expected 0

It might just be a problem with how is the test designed and executed
without `./` prefix.

The test 503 test failure is the one I have described in previous
email, Perl changes related.

The test 501 failure seems test caused as well. It is the second
AT_CHECK failing here:

    # Make sure at-path contains something valid, and let the test suite
    # display it when verbose.  And fail, skipping would too easily hide
    # problems.
    AT_CHECK([sed -n ["s,^.*\`\\(/[^']*\\)'.*,\\1,p"] stdout], [0], [stdout])
    AT_CHECK([test -f "`sed -n 1p stdout`"])

What looks dubious to me though is the fist AT_CHECK. It is checking
the contents of stdout file while at the same time logging the output
to the same stdout file! If you actually run the test commands
manually from command line, it will work OK. I think this is a test
design failure.


--
VH

Loading...