GNU bug report logs - #11512
Testsuite summary for GNU Automake 1.12

Previous Next

Full log

View this message in rfc822 format

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Guido Trentalancia <guido <at> trentalancia.com>
Cc: 11512 <at> debbugs.gnu.org
Subject: bug#11512: Testsuite summary for GNU Automake 1.12
Date: Sun, 27 May 2012 20:01:07 +0200

tags 11512 moreinfo
severity 11512 minor
thanks

Hi Guido, thanks for the report, and sorry for the delay.

On 05/18/2012 08:40 PM, Guido Trentalancia wrote:
> ============================================================================
> Testsuite summary for GNU Automake 1.12
> ============================================================================
> # TOTAL: 2968
> # PASS:  2833
> # SKIP:  89
> # XFAIL: 42
> # FAIL:  4
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See ./test-suite.log
> Please report to bug-automake <at> gnu.org
> ============================================================================
>
What system are you on exactly?  A lots of useful debugging information
about your system and the tools you are using should have been saved by
the test harness in the 't/get-sysconf.log' file; could you please post
its content here?

> ./lib/test-driver: line 95:  8767 Segmentation fault      "$@" >
> $log_file 2>&1
> FAIL: t/pm/Condition-t.pl
> 
> ./lib/test-driver: line 95:  8815 Segmentation fault      "$@" >
> $log_file 2>&1
> FAIL: t/pm/DisjConditions-t.pl
>
Huh?  This sounds like you perl is segfaulting when executing these tests ...
Strange.  Does this happen reliably and consistently, or in a racy way?
Does it happens also if you run run the test cases by hand?  As with:

  $ perl -Mstrict -I lib -w t/pm/DisjConditions-t.pl

> FAIL: t/cond29.sh
> 
> FAIL: t/cond29
> ==============
> 
> Running from installcheck: no
> Using TAP: no
> PATH
> = /usr/src/automake-1.12/t/ax:/usr/src/automake-1.12/t/wrap:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
> ++ pwd
> /usr/src/automake-1.12/t/cond29.dir
> + echo AC_PROG_CC
> + cat
> + ulimit -v 1
> + sh -c :
> ./t/cond29.sh: line 39:   613 Killed                  sh -c ":"
> + ulimit -v 150000
> + sh -c :
> + ulimit -v 150000
>
>  [SNIP]
>
> + echo 'AM_CONDITIONAL([C24], [:])'
> + aclocal-1.12 -Werror
> + automake-1.12 --foreign -Werror -Wall
> Out of memory!
> ./t/cond29.sh: line 61:   686 Segmentation fault      $AUTOMAKE
> + exit_status=139
>
What happens if you raise the ulimit above to (say) 500000?  What if you
bing it down to (say) 50000?  Or 10000?

> + set +e
> + cd /usr/src/automake-1.12
> + test no = yes
> + case $am_explicit_skips in
> + test 139 -eq 0
> + keep_testdirs=yes
> + am_keeping_testdirs
> + case $keep_testdirs in
> + return 0
> + set +x
> cond29: exit 139
> 

Regards,
  Stefano

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.