[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Autoconf 2.64] testsuite: 182 failed
From: |
Ralf Wildenhues |
Subject: |
Re: [GNU Autoconf 2.64] testsuite: 182 failed |
Date: |
Fri, 28 Aug 2009 20:06:43 +0200 |
User-agent: |
Mutt/1.5.20 (2009-08-09) |
Hello Frederik,
thanks for the report.
* Frederik Himpe wrote on Sat, Aug 15, 2009 at 10:41:56PM CEST:
> On Mandriva Linux 2010.0 Cooker, the autoconf 2.64 test number 182
> fails.
> I also found this:
> $ cat micro-suite.log
> # -*- compilation -*-
> 4. micro-suite.at:11: testing ...
> /micro-suite.at:12: kill -$signal $suite_pid
> --- /dev/null 2008-05-30 12:20:24.000000000 +0200
> +++
> /home/fhimpe/autoconf/BUILD/autoconf-2.64/tests/testsuite.dir/182/micro-suite.dir/at-groups/4/stderr
> 2009-08-15 22:27:40.000000000 +0200
> @@ -0,0 +1 @@
> +/home/fhimpe/autoconf/BUILD/autoconf-2.64/tests/testsuite.dir/182/micro-suite.dir/at-groups/4/test-source:
> line 15: kill: : invalid signal specification
Hmpf. What? Somehow, the value of the $signal environment variable is
not transported from the shell running the outer testsuite test group to
the shell running the inner testsuite test group.
Any chance you use or unset the $signal variable in your shell startup
files?
> /micro-suite.at:12: exit code was 1, expected 0
> 4. micro-suite.at:11: 4. killer test (micro-suite.at:11): FAILED
> (micro-suite.at:12)
>
> $ /bin/sh --version
> GNU bash, version 4.0.24(1)-release (x86_64-mandriva-linux-gnu)
I cannot reproduce this failure with this exact shell.
Otherwise, this particular failure is not a big problem for Autoconf,
this test exercises the experimental new parallel Autotest code.
Cheers,
Ralf