[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Václav Haisman
Subject: Re: [GNU Autoconf 2.69] testsuite: 38 501 503 failed
Date: Thu, 8 Jun 2017 01:25:32 +0200

On 7 June 2017 at 21:02, Dennis Clarke <address@hidden> 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
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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]