GNU bug report logs - #12041
Issues running the testsuite as root

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 12041 in the body.
You can then email your comments to 12041 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: bug-automake <at> gnu.org
Subject: GNU Automake 1.12.2 - FAIL 4 tests on SunOS5.10_sparcv9_64-bit
Date: Tue, 24 Jul 2012 08:25:40 -0400

[Message part 1 (text/plain, inline)]

n.b.: see attached self-check-exit.log.gz 
      and GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test.log.gz
      and GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test-suite.log.gz

The final count at the bottom of a *over* 24 hour long test run was : 

============================================================================
Testsuite summary for GNU Automake 1.12.2
============================================================================
# TOTAL: 2578
# PASS:  2221
# SKIP:  307
# XFAIL: 46
# FAIL:  4
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
Please report to bug-automake <at> gnu.org
============================================================================

I go looking for "test-suite.log" and find these : 

bash-3.2# find . -type f -name test-suite.log
./test-suite.log
./t/parallel-tests-many.dir/test-suite.log
./t/tap-bad-prog.dir/test-suite.log

Not very helpful given this : 

bash-3.2# find . -type f -name test-suite.log | xargs wc -l 
   37162 ./test-suite.log
      14 ./t/parallel-tests-many.dir/test-suite.log
      35 ./t/tap-bad-prog.dir/test-suite.log
   37211 total

So I scroll back up the xterm until I see : 

FAIL: t/self-check-exit.tap 33 - syntax error 1
FAIL: t/self-check-exit.tap 34 - syntax error 2
FAIL: t/self-check-explicit-skips.sh

..and a little further up I see : 

FAIL: t/primary-prefix-couples-force-valid.sh


So then, from the top let's see if there is any info to work with here. 




bash-3.2# find . -type f | grep "primary-prefix-couples-force-valid"
./t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a
./t/primary-prefix-couples-force-valid.dir/_inst/lib/foo
./t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h
./t/primary-prefix-couples-force-valid.dir/missing
./t/primary-prefix-couples-force-valid.dir/libquux.c
./t/primary-prefix-couples-force-valid.dir/depcomp
./t/primary-prefix-couples-force-valid.dir/configure
./t/primary-prefix-couples-force-valid.dir/foo.c
./t/primary-prefix-couples-force-valid.dir/install-sh
./t/primary-prefix-couples-force-valid.dir/configure.ac
./t/primary-prefix-couples-force-valid.dir/Makefile
./t/primary-prefix-couples-force-valid.dir/aclocal.m4
./t/primary-prefix-couples-force-valid.dir/.deps/libquux.Po
./t/primary-prefix-couples-force-valid.dir/.deps/foo.Po
./t/primary-prefix-couples-force-valid.dir/config.log
./t/primary-prefix-couples-force-valid.dir/autom4te.cache/output.1
./t/primary-prefix-couples-force-valid.dir/autom4te.cache/traces.0
./t/primary-prefix-couples-force-valid.dir/autom4te.cache/requests
./t/primary-prefix-couples-force-valid.dir/autom4te.cache/output.0
./t/primary-prefix-couples-force-valid.dir/autom4te.cache/traces.1
./t/primary-prefix-couples-force-valid.dir/foo
./t/primary-prefix-couples-force-valid.dir/Makefile.am
./t/primary-prefix-couples-force-valid.dir/libquux.a
./t/primary-prefix-couples-force-valid.dir/libquux.o
./t/primary-prefix-couples-force-valid.dir/bar.h
./t/primary-prefix-couples-force-valid.dir/foo.o
./t/primary-prefix-couples-force-valid.dir/config.status
./t/primary-prefix-couples-force-valid.dir/Makefile.in
./t/primary-prefix-couples-force-valid.log
./t/primary-prefix-couples-force-valid.sh
./t/primary-prefix-couples-force-valid.trs
bash-3.2# wc -l ./t/primary-prefix-couples-force-valid.log
      93 ./t/primary-prefix-couples-force-valid.log
bash-3.2# 
bash-3.2# 
bash-3.2# cat ./t/primary-prefix-couples-force-valid.log
Running from installcheck: no
Using TAP: no
PATH = /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin:/opt/studio/SOS12/SUNWspro/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/dt/bin:/usr/openwin/bin:/opt/schily/bin
+++ pwd
/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir
+ cat
+ cat
+ cat
+ cat
+ :
+ aclocal-1.12 -Werror
+ automake-1.12 --foreign -Werror -Wall -a
configure.ac:5: installing './ar-lib'
+ autoconf
++ pwd
+ cwd=/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir
+ ./configure --prefix=/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst
checking for a BSD-compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking for gcc... /opt/studio/SOS12/SUNWspro/bin/cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether /opt/studio/SOS12/SUNWspro/bin/cc accepts -g... yes
checking for /opt/studio/SOS12/SUNWspro/bin/cc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of /opt/studio/SOS12/SUNWspro/bin/cc... none
checking the archiver (/usr/ccs/bin/ar) interface... ar
checking for ranlib... ranlib
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
+ make install
source='libquux.c' object='libquux.o' libtool=no \
DEPDIR=.deps depmode=none /bin/bash ./depcomp \
/opt/studio/SOS12/SUNWspro/bin/cc -DPACKAGE_NAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_TARNAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"primary-prefix-couples-force-valid\ 1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"primary-prefix-couples-force-valid\" -DVERSION=\"1.0\" -I.      -g -c libquux.c
rm -f libquux.a
/usr/ccs/bin/ar cru libquux.a libquux.o 
ranlib libquux.a
source='foo.c' object='foo.o' libtool=no \
DEPDIR=.deps depmode=none /bin/bash ./depcomp \
/opt/studio/SOS12/SUNWspro/bin/cc -DPACKAGE_NAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_TARNAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"primary-prefix-couples-force-valid\ 1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"primary-prefix-couples-force-valid\" -DVERSION=\"1.0\" -I.      -g -c foo.c
/opt/studio/SOS12/SUNWspro/bin/cc  -g   -o foo foo.o  
 ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin'
 ./install-sh -c -m 644  libquux.a '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin'
 ( cd '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin' && ranlib libquux.a )
 ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib'
  ./install-sh -c foo '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib'
 ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec'
 ./install-sh -c -m 644 bar.h '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec'
+ make installcheck
(cd '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst' && find .);: For debugging.
.
./bin
./bin/libquux.a
./lib
./lib/foo
./libexec
./libexec/bar.h
ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
-rwxr-xr-x   1 root     root        7944 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo
test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
test -x '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a'
-rw-r--r--   1 root     root        2360 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a
test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a'
ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
-rw-r--r--   1 root     root           0 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h
test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
test ! -x '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
*** Error code 1
make: Fatal error: Command failed for target `test'
+ exit_status=1
+ set +e
+ cd /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ test no = yes
+ case $am_explicit_skips in
+ test 1 -eq 0
+ keep_testdirs=yes
+ am_keeping_testdirs
+ case $keep_testdirs in
+ return 0
+ set +x
primary-prefix-couples-force-valid: exit 1
bash-3.2# 



OKay, so that was the first fail. 


Next was : 


bash-3.2# find . -type f | grep "self-check-exit"
./t/self-check-exit.trs
./t/self-check-exit.log
./t/self-check-exit.tap
bash-3.2# 
bash-3.2# wc -l ./t/self-check-exit.log
    1438 ./t/self-check-exit.log
bash-3.2# 


Well I don't think that putting 1430+ lines of log bits in here would be reasonable so therefore maybe I can attach it ? 


Lastly we have this one : 


bash-3.2# find . -type f | grep "self-check-explicit-skips"
./t/self-check-explicit-skips.sh
./t/self-check-explicit-skips.trs
./t/self-check-explicit-skips.log
bash-3.2# wc -l ./t/self-check-explicit-skips.log
     123 ./t/self-check-explicit-skips.log
bash-3.2# 


That log file is not too unreasonable .. thus here it is : 


bash-3.2# cat ./t/self-check-explicit-skips.log
Running from installcheck: no
Using TAP: no
PATH = /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin:/opt/studio/SOS12/SUNWspro/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/dt/bin:/usr/openwin/bin:/opt/schily/bin
+++ pwd
/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ set +e
+ unset am_explicit_skips stderr_fileno_
+ run_dummy_test '(exit 77); exit 77'
+ env /bin/bash -c '
    am_create_testdir=no
    . ./defs
    (exit 77); exit 77
  ' dummy.sh
Running from installcheck: no
Using TAP: no
PATH = /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin:/opt/studio/SOS12/SUNWspro/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/dt/bin:/usr/openwin/bin:/opt/schily/bin
+++ pwd
/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ _am_exit 77
+ set +e
+ test 77 = 77
+ am__test_skipped=yes
+ exit 77
+ exit 77
+ _am_exit 77
+ set +e
+ test 77 = 77
+ am__test_skipped=yes
+ exit 77
+ exit 77
+ exit_status=77
+ set +e
+ cd /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ test no = yes
+ case $am_explicit_skips in
+ test 77 -eq 0
+ keep_testdirs=yes
+ am_keeping_testdirs
+ case $keep_testdirs in
+ return 0
+ set +x
dummy: exit 77
+ test 77 -eq 77
+ run_dummy_test 'sh -c "exit 77"' am_explicit_skips=no
+ env am_explicit_skips=no /bin/bash -c '
    am_create_testdir=no
    . ./defs
    sh -c "exit 77"
  ' dummy.sh
Running from installcheck: no
Using TAP: no
PATH = /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin:/opt/studio/SOS12/SUNWspro/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/dt/bin:/usr/openwin/bin:/opt/schily/bin
+++ pwd
/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ sh -c 'exit 77'
+ exit_status=77
+ set +e
+ cd /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ test no = yes
+ case $am_explicit_skips in
+ test 77 -eq 0
+ keep_testdirs=yes
+ am_keeping_testdirs
+ case $keep_testdirs in
+ return 0
+ set +x
dummy: exit 77
+ test 77 -eq 77
+ run_dummy_test '(exit 77); exit 77' am_explicit_skips=yes
+ env am_explicit_skips=yes /bin/bash -c '
    am_create_testdir=no
    . ./defs
    (exit 77); exit 77
  ' dummy.sh
Running from installcheck: no
Using TAP: no
PATH = /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin:/opt/studio/SOS12/SUNWspro/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/dt/bin:/usr/openwin/bin:/opt/schily/bin
+++ pwd
/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ _am_exit 77
+ set +e
+ test 77 = 77
+ am__test_skipped=yes
+ exit 77
+ exit 77
+ _am_exit 77
+ set +e
+ test 77 = 77
+ am__test_skipped=yes
+ exit 77
+ exit 77
+ exit_status=77
+ set +e
+ cd /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ test no = yes
+ case $am_explicit_skips in
+ test 77 -eq 77
+ test yes '!=' yes
+ test 77 -eq 0
+ keep_testdirs=yes
+ am_keeping_testdirs
+ case $keep_testdirs in
+ return 0
+ set +x
dummy: exit 77
+ test 77 -eq 78
+ _am_exit 1
+ set +e
+ test 77 = 1
+ exit 1
+ exit 1
+ exit_status=1
+ set +e
+ cd /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit
+ test no = yes
+ case $am_explicit_skips in
+ test 1 -eq 0
+ keep_testdirs=yes
+ am_keeping_testdirs
+ case $keep_testdirs in
+ return 0
+ set +x
self-check-explicit-skips: exit 1


Any other info required ?  Let me know.

Dennis Clarke
dclarke <at> blastwave.org

[self-check-exit.log.gz (application/x-gzip, attachment)]

[GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test.log.gz (application/x-gzip, attachment)]

[GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test-suite.log.gz (application/x-gzip, attachment)]

Message #8 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org
Subject: Issues running the testsuite as root (was: Re: bug#12041: GNU Automake
	1.12.2 - FAIL 4 tests on SunOS5.10_sparcv9_64-bit)
Date: Tue, 24 Jul 2012 14:48:35 +0200

severity 12041 minor
retitle 12041 Issues running the testsuite as root
thanks

Hi Dennis, thanks for the report.

On 07/24/2012 02:25 PM, Dennis Clarke wrote:
> 
> 
> n.b.: see attached self-check-exit.log.gz 
>       and GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test.log.gz
>       and GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test-suite.log.gz
> 
> The final count at the bottom of a *over* 24 hour long test run was : 
> 
> ============================================================================
> Testsuite summary for GNU Automake 1.12.2
> ============================================================================
> # TOTAL: 2578
> # PASS:  2221
> # SKIP:  307
> # XFAIL: 46
> # FAIL:  4
> # XPASS: 0
> # ERROR: 0
> ============================================================================
> See ./test-suite.log
> Please report to bug-automake <at> gnu.org
> ============================================================================
> 
> I go looking for "test-suite.log" and find these : 
> 
> bash-3.2# find . -type f -name test-suite.log
> ./test-suite.log
> ./t/parallel-tests-many.dir/test-suite.log
> ./t/tap-bad-prog.dir/test-suite.log
> 
> Not very helpful given this : 
> 
> bash-3.2# find . -type f -name test-suite.log | xargs wc -l 
>    37162 ./test-suite.log
>       14 ./t/parallel-tests-many.dir/test-suite.log
>       35 ./t/tap-bad-prog.dir/test-suite.log
>    37211 total
> 
> So I scroll back up the xterm until I see : 
> 
> FAIL: t/self-check-exit.tap 33 - syntax error 1
> FAIL: t/self-check-exit.tap 34 - syntax error 2
> FAIL: t/self-check-explicit-skips.sh
>
These are known testsuite issues (not real bugs in automake), and have
already been solved in the development version of Automake.  So we don't
need to worry about them.

> ..and a little further up I see : 
> 
> FAIL: t/primary-prefix-couples-force-valid.sh
>
This is new :-/

> bash-3.2# cat ./t/primary-prefix-couples-force-valid.log
>
> Running from installcheck: no
> Using TAP: no
> PATH = /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin:/opt/studio/SOS12/SUNWspro/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/dt/bin:/usr/openwin/bin:/opt/schily/bin
> +++ pwd
> /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir
> + cat
> + cat
> + cat
> + cat
> + :
> + aclocal-1.12 -Werror
> + automake-1.12 --foreign -Werror -Wall -a
> configure.ac:5: installing './ar-lib'
> + autoconf
> ++ pwd
> + cwd=/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir
> + ./configure --prefix=/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst
> checking for a BSD-compatible install... ./install-sh -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> checking for gawk... no
> checking for mawk... no
> checking for nawk... nawk
> checking whether make sets $(MAKE)... yes
> checking for gcc... /opt/studio/SOS12/SUNWspro/bin/cc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... no
> checking whether /opt/studio/SOS12/SUNWspro/bin/cc accepts -g... yes
> checking for /opt/studio/SOS12/SUNWspro/bin/cc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of /opt/studio/SOS12/SUNWspro/bin/cc... none
> checking the archiver (/usr/ccs/bin/ar) interface... ar
> checking for ranlib... ranlib
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: executing depfiles commands
> + make install
> source='libquux.c' object='libquux.o' libtool=no \
> DEPDIR=.deps depmode=none /bin/bash ./depcomp \
> /opt/studio/SOS12/SUNWspro/bin/cc -DPACKAGE_NAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_TARNAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"primary-prefix-couples-force-valid\ 1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"primary-prefix-couples-force-valid\" -DVERSION=\"1.0\" -I.      -g -c libquux.c
> rm -f libquux.a
> /usr/ccs/bin/ar cru libquux.a libquux.o 
> ranlib libquux.a
> source='foo.c' object='foo.o' libtool=no \
> DEPDIR=.deps depmode=none /bin/bash ./depcomp \
> /opt/studio/SOS12/SUNWspro/bin/cc -DPACKAGE_NAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_TARNAME=\"primary-prefix-couples-force-valid\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"primary-prefix-couples-force-valid\ 1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"primary-prefix-couples-force-valid\" -DVERSION=\"1.0\" -I.      -g -c foo.c
> /opt/studio/SOS12/SUNWspro/bin/cc  -g   -o foo foo.o  
>  ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin'
>  ./install-sh -c -m 644  libquux.a '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin'
>  ( cd '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin' && ranlib libquux.a )
>  ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib'
>   ./install-sh -c foo '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib'
>  ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec'
>  ./install-sh -c -m 644 bar.h '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec'
> + make installcheck
> (cd '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst' && find .);: For debugging.
> .
> ./bin
> ./bin/libquux.a
> ./lib
> ./lib/foo
> ./libexec
> ./libexec/bar.h
> ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
> -rwxr-xr-x   1 root     root        7944 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo
> test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
> test -x '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
> ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a'
> -rw-r--r--   1 root     root        2360 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a
> test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a'
> ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
> -rw-r--r--   1 root     root           0 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h
> test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
> test ! -x '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
> *** Error code 1
> make: Fatal error: Command failed for target `test'
>
Huh?  According to the output of "ls -l" above, the installed file
'libexec/bar.h' is *not* executable.  So why is this test failing?

Hah!  It happens because you are running the test as root.  My advice
is: don't do that.  Still, since this seems to be the only spurious
failure experienced due to the extra privileges, it might be worth
fixing it, since that would be pretty easy to so.  So I'm not closing
this bug report yet.

> Any other info required ?  Let me know.
>
Just to be extra-sure: does the test pass if you run it as a non-root
user?  If you don't have to check this, no big deal, as I'm already
pretty sure my diagnosis is correct.

Thanks,
  Stefano

Message #15 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root (was: Re: bug#12041: GNU
	Automake 1.12.2 - FAIL 4 tests on SunOS5.10_sparcv9_64-bit)
Date: Tue, 24 Jul 2012 09:33:22 -0400

First comment : wow. that was fast. :-) 

----- Original Message -----
From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Date: Tuesday, July 24, 2012 8:48 am
Subject: Issues running the testsuite as root (was: Re: bug#12041: GNU Automake 1.12.2 - FAIL 4 tests on SunOS5.10_sparcv9_64-bit)
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org


> severity 12041 minor
> retitle 12041 Issues running the testsuite as root
> thanks

beauty. I know I know. Shouldn't do that.  In fact I rarely do, however, and this may be of some value, I did the whole build and then testsuite as regular user ( me ) and had errors also. Then I thought, hrmmmm, what if I retry this as root? Not my most brilliant thinking but a reasonable experiment anyways. 

At the very least it revealed something. 

> 
> Hi Dennis, thanks for the report.

I try.  ;-)

> 
> On 07/24/2012 02:25 PM, Dennis Clarke wrote:
> > 
> > 
> > n.b.: see attached self-check-exit.log.gz 
> >       and GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test.log.gz
> >       and GNU_Automake_1.12.2_SunOS5.10_sparcv9_64-bit.test-suite.log.gz
> > 
> > The final count at the bottom of a *over* 24 hour long test run was 
> : 
> > 
> > ============================================================================
> > Testsuite summary for GNU Automake 1.12.2
> > ============================================================================
> > # TOTAL: 2578
> > # PASS:  2221
> > # SKIP:  307
> > # XFAIL: 46
> > # FAIL:  4
> > # XPASS: 0
> > # ERROR: 0
> > ============================================================================
> > See ./test-suite.log
> > Please report to bug-automake <at> gnu.org
> > ============================================================================

 < snippage >

> > 
> > So I scroll back up the xterm until I see : 
> > 
> > FAIL: t/self-check-exit.tap 33 - syntax error 1
> > FAIL: t/self-check-exit.tap 34 - syntax error 2
> > FAIL: t/self-check-explicit-skips.sh
> >
> These are known testsuite issues (not real bugs in automake), and have
> already been solved in the development version of Automake.  So we don't
> need to worry about them.

  \o/ 

  yay

Okay .. this is a good thing. I guess we can expect a release on that in
the near future ? 

> > ..and a little further up I see : 
> > 
> > FAIL: t/primary-prefix-couples-force-valid.sh
> >
> This is new :-/

Had to be a winner in here somewhere.  However, yes, smack me upside the head
for doing this as root. That is just wrong according to the dogma of UNIX and
I should correct my self accordingly.  

> > bash-3.2# cat ./t/primary-prefix-couples-force-valid.log
> >
> > Running from installcheck: no
> > Using TAP: no
> > PATH = /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/ax:/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/wrap:/usr/local/bin:/usr/xpg6/bin:/usr/xpg4/bin:/usr/ccs/bin:/opt/studio/SOS12/SUNWspro/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/dt/bin:/usr/openwin/bin:/opt/schily/bin
> > +++ pwd
> > /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir
> > + cat
> > + cat
> > + cat
> > + cat
> > + :
> > + aclocal-1.12 -Werror
> > + automake-1.12 --foreign -Werror -Wall -a
> > configure.ac:5: installing './ar-lib'
> > + autoconf
> > ++ pwd
> > + cwd=/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir
> > + ./configure --prefix=/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst
> > checking for a BSD-compatible install... ./install-sh -c
> > checking whether build environment is sane... yes
> > checking for a thread-safe mkdir -p... ./install-sh -c -d
> > checking for gawk... no
> > checking for mawk... no
> > checking for nawk... nawk
> > checking whether make sets $(MAKE)... yes
> > checking for gcc... /opt/studio/SOS12/SUNWspro/bin/cc
> > checking whether the C compiler works... yes
> > checking for C compiler default output file name... a.out
> > checking for suffix of executables... 
> > checking whether we are cross compiling... no
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... no
> > checking whether /opt/studio/SOS12/SUNWspro/bin/cc accepts -g... yes
> > checking for /opt/studio/SOS12/SUNWspro/bin/cc option to accept ISO 
> C89... none needed
> > checking for style of include used by make... GNU
> > checking dependency style of /opt/studio/SOS12/SUNWspro/bin/cc... none
> > checking the archiver (/usr/ccs/bin/ar) interface... ar
> > checking for ranlib... ranlib
> > checking that generated files are newer than configure... done
> > configure: creating ./config.status
> > config.status: creating Makefile
> > config.status: executing depfiles commands
> > + make install
> > source='libquux.c' object='libquux.o' libtool=no \
> > DEPDIR=.deps depmode=none /bin/bash ./depcomp \
> > /opt/studio/SOS12/SUNWspro/bin/cc 
> -DPACKAGE_NAME=\"primary-prefix-couples-force-valid\" 
> -DPACKAGE_TARNAME=\"primary-prefix-couples-force-valid\" 
> -DPACKAGE_VERSION=\"1.0\" 
> -DPACKAGE_STRING=\"primary-prefix-couples-force-valid\ 1.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"primary-prefix-couples-force-valid\" -DVERSION=\"1.0\" -I. 
>      -g -c libquux.c
> > rm -f libquux.a
> > /usr/ccs/bin/ar cru libquux.a libquux.o 
> > ranlib libquux.a
> > source='foo.c' object='foo.o' libtool=no \
> > DEPDIR=.deps depmode=none /bin/bash ./depcomp \
> > /opt/studio/SOS12/SUNWspro/bin/cc 
> -DPACKAGE_NAME=\"primary-prefix-couples-force-valid\" 
> -DPACKAGE_TARNAME=\"primary-prefix-couples-force-valid\" 
> -DPACKAGE_VERSION=\"1.0\" 
> -DPACKAGE_STRING=\"primary-prefix-couples-force-valid\ 1.0\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"primary-prefix-couples-force-valid\" -DVERSION=\"1.0\" -I. 
>      -g -c foo.c
> > /opt/studio/SOS12/SUNWspro/bin/cc  -g   -o foo foo.o  
> >  ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin'
> >  ./install-sh -c -m 644  libquux.a '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin'
> >  ( cd 
> '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin' 
> && ranlib libquux.a )
> >  ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib'
> >   ./install-sh -c foo '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib'
> >  ./install-sh -c -d '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec'
> >  ./install-sh -c -m 644 bar.h '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec'
> > + make installcheck
> > (cd 
> '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst' 
> && find .);: For debugging.
> > .
> > ./bin
> > ./bin/libquux.a
> > ./lib
> > ./lib/foo
> > ./libexec
> > ./libexec/bar.h
> > ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
> > -rwxr-xr-x   1 root     root        7944 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo
> > test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
> > test -x '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/lib/foo'
> > ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a'
> > -rw-r--r--   1 root     root        2360 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a
> > test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/bin/libquux.a'
> > ls -l '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
> > -rw-r--r--   1 root     root           0 Jul 24 00:52 /usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h
> > test -f '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
> > test ! -x '/usr/local/build/automake-1.12.2_SunOS5.10_sparcv9_64-bit/t/primary-prefix-couples-force-valid.dir/_inst/libexec/bar.h'
> > *** Error code 1
> > make: Fatal error: Command failed for target `test'
> >
> Huh?  According to the output of "ls -l" above, the installed file
> 'libexec/bar.h' is *not* executable.  So why is this test failing?

Well I figure a header should be just chmod 644 .  makes sense right ? 

> 
> Hah!  It happens because you are running the test as root.  My advice
> is: don't do that. 

   yes Sir.   ( I hang my head in shame ) 

> Still, since this seems to be the only spurious
> failure experienced due to the extra privileges, it might be worth
> fixing it, since that would be pretty easy to so.  So I'm not closing
> this bug report yet.
> 
> > Any other info required ?  Let me know.
> >
> Just to be extra-sure: does the test pass if you run it as a non-root
> user?  If you don't have to check this, no big deal, as I'm already
> pretty sure my diagnosis is correct.

I will go back and give that a go, again.  Will let you know for sure.
However this is an old slow Sun Sparc Netra box and it will take bloody
forever to run. Like 36 hours or so. 

Dennis 

Message #18 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 15:38:20 +0200

On 07/24/2012 03:33 PM, Dennis Clarke wrote:
>
>> These are known testsuite issues (not real bugs in automake), and have
>> already been solved in the development version of Automake.  So we don't
>> need to worry about them.
>
> Okay .. this is a good thing. I guess we can expect a release on that in
> the near future ?
>
Couple of weeks for the next maintenance version (1.12.3) I'd say.  Couple
of months at least for the next major version (1.13).

>> Just to be extra-sure: does the test pass if you run it as a non-root
>> user?  If you don't have to check this, no big deal, as I'm already
>> pretty sure my diagnosis is correct.
> 
> I will go back and give that a go, again.  Will let you know for sure.
> However this is an old slow Sun Sparc Netra box and it will take bloody
> forever to run. Like 36 hours or so. 
>
Oh, don't bother re-running the whole testsuite!  Just the failed test
should be enough.  You might re-run the whole testsuite once 1.12.3 is
out, maybe, if you have enough patience.

Thanks,
  Stefano

Message #21 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 09:59:26 -0400

> On 07/24/2012 03:33 PM, Dennis Clarke wrote:
> >
> >> These are known testsuite issues (not real bugs in automake), and have
> >> already been solved in the development version of Automake.  So we 
> don't
> >> need to worry about them.
> >
> > Okay .. this is a good thing. I guess we can expect a release on 
> that in
> > the near future ?
> >
> Couple of weeks for the next maintenance version (1.12.3) I'd say.  Couple
> of months at least for the next major version (1.13).

beauty. 

To me a testsuite that goes over thousands of tests is a damn good thing and thus I am fine with running the whole show. 

> >> Just to be extra-sure: does the test pass if you run it as a non-root
> >> user?  If you don't have to check this, no big deal, as I'm already
> >> pretty sure my diagnosis is correct.
> > 
> > I will go back and give that a go, again.  Will let you know for sure.
> > However this is an old slow Sun Sparc Netra box and it will take bloody
> > forever to run. Like 36 hours or so. 
> >
> Oh, don't bother re-running the whole testsuite!  Just the failed test
> should be enough.  You might re-run the whole testsuite once 1.12.3 is
> out, maybe, if you have enough patience.
> 


However, for just right now, how would I run just that one test? 

Dennis 

Message #24 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 16:05:47 +0200

On 07/24/2012 03:59 PM, Dennis Clarke wrote:
> 
> However, for just right now, how would I run just that one test? 
>
In this case:

    make check TESTS=t/primary-prefix-couples-force-valid

Regards,
  Stefano

Message #27 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 10:42:45 -0400

> On 07/24/2012 03:59 PM, Dennis Clarke wrote:
> > 
> > However, for just right now, how would I run just that one test? 
> >
> In this case:
> 
>     make check TESTS=t/primary-prefix-couples-force-valid

I have to fix a pile of little things, because of course, I did this as root previously and now that test fails in many cute ways because of that. 

[ here I find wall, smack head to wall, live and learn what I already bloody knew ]

so .. I have that running now.  Will let you know when, if, it finishes.

Dennis 

Message #30 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 11:14:09 -0400

> On 07/24/2012 03:59 PM, Dennis Clarke wrote:
> > 
> > However, for just right now, how would I run just that one test? 
> >
> In this case:
> 
>     make check TESTS=t/primary-prefix-couples-force-valid

Is this really just one test ? 

Thus far I see this : 

 $ make check TESTS=t/primary-prefix-couples-force-valid
make  t/wrap/aclocal-1.12 t/wrap/automake-1.12 t/ax/test-init.sh   t/ax/plain-functions.sh   t/ax/tap-functions.sh \
  defs-static
`t/wrap/aclocal-1.12' is up to date.
`t/wrap/automake-1.12' is up to date.
`t/ax/test-init.sh' is up to date.
`t/ax/plain-functions.sh' is up to date.
`t/ax/tap-functions.sh' is up to date.
`defs-static' is up to date.
make  check-TESTS check-local
SKIP: t/get-sysconf.sh
XFAIL: t/pm/Cond2.pl
XFAIL: t/pm/Cond3.pl
PASS: t/pm/Condition.pl
SKIP: t/pm/Condition-t.pl
XFAIL: t/pm/DisjCon2.pl
XFAIL: t/pm/DisjCon3.pl
PASS: t/pm/DisjConditions.pl
SKIP: t/pm/DisjConditions-t.pl
PASS: t/pm/Version.pl
XFAIL: t/pm/Version2.pl
XFAIL: t/pm/Version3.pl
PASS: t/pm/Wrap.pl
cond: skipped test: performance tests not explicitly enabled
SKIP: t/perf/cond.sh
testsuite-recheck: skipped test: performance tests not explicitly enabled
SKIP: t/perf/testsuite-recheck.sh
testsuite-summary: skipped test: performance tests not explicitly enabled
SKIP: t/perf/testsuite-summary.sh
XFAIL: t/instspc.tap 1 - squote in builddir # TODO long-standing limitation
XFAIL: t/instspc.tap 2 - squote in destdir # TODO long-standing limitation
XFAIL: t/instspc.tap 3 - dquote in builddir # TODO long-standing limitation
XFAIL: t/instspc.tap 4 - dquote in destdir # TODO long-standing limitation
XFAIL: t/instspc.tap 5 - bquote in builddir # TODO long-standing limitation
XFAIL: t/instspc.tap 6 - bquote in destdir # TODO long-standing limitation
XFAIL: t/instspc.tap 7 - sharp in builddir # TODO long-standing limitation
XFAIL: t/instspc.tap 8 - sharp in destdir # TODO long-standing limitation
XFAIL: t/instspc.tap 9 - dollar in builddir # TODO long-standing limitation
XFAIL: t/instspc.tap 10 - dollar in destdir # TODO long-standing limitation
PASS: t/instspc.tap 11 - bang in builddir
PASS: t/instspc.tap 12 - bang in destdir
XFAIL: t/instspc.tap 13 - bslash in builddir # TODO long-standing limitation
PASS: t/instspc.tap 14 - bslash in destdir
XFAIL: t/instspc.tap 15 - ampersand in builddir # TODO long-standing limitation
PASS: t/instspc.tap 16 - ampersand in destdir
PASS: t/instspc.tap 17 - percent in builddir
PASS: t/instspc.tap 18 - percent in destdir
PASS: t/instspc.tap 19 - leftpar in builddir
PASS: t/instspc.tap 20 - leftpar in destdir
PASS: t/instspc.tap 21 - rightpar in builddir
PASS: t/instspc.tap 22 - rightpar in destdir
PASS: t/instspc.tap 23 - pipe in builddir
PASS: t/instspc.tap 24 - pipe in destdir
PASS: t/instspc.tap 25 - caret in builddir
PASS: t/instspc.tap 26 - caret in destdir
PASS: t/instspc.tap 27 - tilde in builddir
PASS: t/instspc.tap 28 - tilde in destdir
PASS: t/instspc.tap 29 - qmark in builddir
PASS: t/instspc.tap 30 - qmark in destdir
PASS: t/instspc.tap 31 - star in builddir
PASS: t/instspc.tap 32 - star in destdir
PASS: t/instspc.tap 33 - plus in builddir
PASS: t/instspc.tap 34 - plus in destdir
PASS: t/instspc.tap 35 - minus in builddir
PASS: t/instspc.tap 36 - minus in destdir
PASS: t/instspc.tap 37 - comma in builddir
PASS: t/instspc.tap 38 - comma in destdir
PASS: t/instspc.tap 39 - colon in builddir
PASS: t/instspc.tap 40 - colon in destdir
PASS: t/instspc.tap 41 - semicol in builddir
PASS: t/instspc.tap 42 - semicol in destdir
PASS: t/instspc.tap 43 - equal in builddir
PASS: t/instspc.tap 44 - equal in destdir
PASS: t/instspc.tap 45 - less in builddir
PASS: t/instspc.tap 46 - less in destdir
PASS: t/instspc.tap 47 - more in builddir
PASS: t/instspc.tap 48 - more in destdir
PASS: t/instspc.tap 49 - at in builddir
PASS: t/instspc.tap 50 - at in destdir
PASS: t/instspc.tap 51 - lqbrack in builddir
PASS: t/instspc.tap 52 - lqbrack in destdir
PASS: t/instspc.tap 53 - rqbrack in builddir
PASS: t/instspc.tap 54 - rqbrack in destdir
PASS: t/instspc.tap 55 - lcbrack in builddir
PASS: t/instspc.tap 56 - lcbrack in destdir
PASS: t/instspc.tap 57 - rcbrack in builddir
PASS: t/instspc.tap 58 - rcbrack in destdir
PASS: t/instspc.tap 59 - space in builddir
PASS: t/instspc.tap 60 - space in destdir
PASS: t/instspc.tap 61 - tab in builddir
PASS: t/instspc.tap 62 - tab in destdir
XFAIL: t/instspc.tap 63 - linefeed in builddir # TODO long-standing limitation
XFAIL: t/instspc.tap 64 - linefeed in destdir # TODO long-standing limitation
PASS: t/instspc.tap 65 - backspace in builddir
PASS: t/instspc.tap 66 - backspace in destdir
PASS: t/instspc.tap 67 - formfeed in builddir
PASS: t/instspc.tap 68 - formfeed in destdir
PASS: t/instspc.tap 69 - carriageret in builddir
PASS: t/instspc.tap 70 - carriageret in destdir
XFAIL: t/instspc.tap 71 - quadrigraph0 in builddir # TODO long-standing limitation
PASS: t/instspc.tap 72 - quadrigraph0 in destdir
PASS: t/instspc.tap 73 - quadrigraph1 in builddir
PASS: t/instspc.tap 74 - quadrigraph1 in destdir
PASS: t/instspc.tap 75 - quadrigraph2 in builddir
PASS: t/instspc.tap 76 - quadrigraph2 in destdir
PASS: t/instspc.tap 77 - quadrigraph3 in builddir
PASS: t/instspc.tap 78 - quadrigraph3 in destdir
PASS: t/instspc.tap 79 - quadrigraph4 in builddir
PASS: t/instspc.tap 80 - quadrigraph4 in destdir
PASS: t/instspc.tap 81 - a_b in builddir
PASS: t/instspc.tap 82 - a_b in destdir
PASS: t/instspc.tap 83 - a__b in builddir
PASS: t/instspc.tap 84 - a__b in destdir
XFAIL: t/instspc.tap 85 - a_lf_b in builddir # TODO long-standing limitation
XFAIL: t/instspc.tap 86 - a_lf_b in destdir # TODO long-standing limitation
PASS: t/instspc.tap 87 - dotdotdot in builddir
PASS: t/instspc.tap 88 - dotdotdot in destdir
PASS: t/instspc.tap 89 - dosdrive in builddir
PASS: t/instspc.tap 90 - dosdrive in destdir
PASS: t/instspc.tap 91 - miscglob1 in builddir
PASS: t/instspc.tap 92 - miscglob1 in destdir
PASS: t/instspc.tap 93 - miscglob2 in builddir
PASS: t/instspc.tap 94 - miscglob2 in destdir
PASS: t/aclocal.sh
PASS: t/aclocal3.sh
PASS: t/aclocal4.sh
PASS: t/aclocal5.sh
PASS: t/aclocal6.sh
PASS: t/aclocal7.sh
PASS: t/aclocal8.sh
PASS: t/aclocal9.sh
PASS: t/acloca10.sh
PASS: t/acloca11.sh
PASS: t/acloca12.sh
PASS: t/acloca13.sh
PASS: t/acloca14.sh
PASS: t/acloca15.sh
PASS: t/acloca16.sh
PASS: t/acloca17.sh
PASS: t/acloca18.sh
PASS: t/acloca19.sh
PASS: t/acloca20.sh
PASS: t/acloca21.sh
PASS: t/acloca22.sh
PASS: t/acloca23.sh
PASS: t/aclocal-acdir.sh
PASS: t/aclocal-install-absdir.sh
PASS: t/aclocal-print-acdir.sh
PASS: t/aclocal-path.sh
PASS: t/aclocal-path-install.sh
PASS: t/aclocal-path-install-serial.sh


... looks like a whole testsuite again.

dc

Message #33 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 18:06:01 +0200

On 07/24/2012 05:14 PM, Dennis Clarke wrote:
> 
>> On 07/24/2012 03:59 PM, Dennis Clarke wrote:
>>>
>>> However, for just right now, how would I run just that one test? 
>>>
>> In this case:
>>
>>     make check TESTS=t/primary-prefix-couples-force-valid
> 
> Is this really just one test ? 
>
Oh no, my bad!  You are not using GNU make, so you have to use a more
complex idiom:

    make check TESTS=t/primary-prefix-couples-force-valid AM_MAKEFLAGS='TESTS="$(TESTS)"'

Thanks, and sorry for the confusion,
  Stefano

Message #36 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 12:11:34 -0400

----- Original Message -----
From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Date: Tuesday, July 24, 2012 12:06 pm
Subject: Re: Issues running the testsuite as root
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org


> On 07/24/2012 05:14 PM, Dennis Clarke wrote:
> > 
> >> On 07/24/2012 03:59 PM, Dennis Clarke wrote:
> >>>
> >>> However, for just right now, how would I run just that one test? 
> >>>
> >> In this case:
> >>
> >>     make check TESTS=t/primary-prefix-couples-force-valid
> > 
> > Is this really just one test ? 
> >
> Oh no, my bad!  You are not using GNU make, so you have to use a more
> complex idiom:
> 
>     make check TESTS=t/primary-prefix-couples-force-valid AM_MAKEFLAGS='TESTS="$(TESTS)"'

see ... lots of magic required depending on the environment. 

I can tell you from experience that dealing with GNU open source software on the Solaris OS is always a fight simply because most of the devs and the configure scripts ( etc etc ) all *assume* you use GNU tools like binutils, make, ar, as, ld, etc etc on and on. When of course you don't, well, confusion and errors pop up all over the place. 

The only real recourse seems to be to run a configure script that issues a ( $SOMEPATH/make --version ) and then tests for output that identifies what make we have. Same with every other little piece. 

Is the effort worth it?

Not really. 

Most people I talk too are fleeing, with hair on fire, away from Oracle Solaris and all its complex expenses and horrible support.  

So .. I'll get off my soapbox now and just go run the tests. Really I do need to have a small collection of GNU tools and they really do need to pass their testsuites.  ( groan ) 

Dennis 
 

Message #39 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org
Subject: Re: Issues running the testsuite as root
Date: Tue, 24 Jul 2012 12:14:00 -0400

----- Original Message -----
From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Date: Tuesday, July 24, 2012 12:06 pm
Subject: Re: Issues running the testsuite as root
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org


> On 07/24/2012 05:14 PM, Dennis Clarke wrote:
> > 
> >> On 07/24/2012 03:59 PM, Dennis Clarke wrote:
> >>>
> >>> However, for just right now, how would I run just that one test? 
> >>>
> >> In this case:
> >>
> >>     make check TESTS=t/primary-prefix-couples-force-valid
> > 
> > Is this really just one test ? 
> >
> Oh no, my bad!  You are not using GNU make, so you have to use a more
> complex idiom:
> 
>     make check TESTS=t/primary-prefix-couples-force-valid AM_MAKEFLAGS='TESTS="$(TESTS)"'

ta da : 

iscbind $ make check TESTS=t/primary-prefix-couples-force-valid AM_MAKEFLAGS='TESTS="$(TESTS)"'
make TESTS="t/primary-prefix-couples-force-valid" t/wrap/aclocal-1.12 t/wrap/automake-1.12 t/ax/test-init.sh   t/ax/plain-functions.sh   t/ax/tap-functions.sh \
  defs-static
`t/wrap/aclocal-1.12' is up to date.
`t/wrap/automake-1.12' is up to date.
`t/ax/test-init.sh' is up to date.
`t/ax/plain-functions.sh' is up to date.
`t/ax/tap-functions.sh' is up to date.
`defs-static' is up to date.
make TESTS="t/primary-prefix-couples-force-valid" check-TESTS check-local
PASS: t/primary-prefix-couples-force-valid.sh
============================================================================
Testsuite summary for GNU Automake 1.12.2
============================================================================
# TOTAL: 1
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================
iscbind $ 

So that sorts out that fake FAIL from earlier. 

Dennis 

Message #42 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org,
	"a >> \"automake-patches <at> gnu.org\"" <automake-patches <at> gnu.org>
Subject: Re: bug#12041: Issues running the testsuite as root
Date: Wed, 25 Jul 2012 12:41:56 +0200

[Message part 1 (text/plain, inline)]

tags 12041 + patch
thanks

Hi Dennis.

Stefano Lattarini wrote:
>
> Hah!  It happens because you are running the test as root.  My advice
> is: don't do that.  Still, since this seems to be the only spurious
> failure experienced due to the extra privileges, it might be worth
> fixing it, since that would be pretty easy to so.  So I'm not closing
> this bug report yet.
>
The attached patch should solve the issue.  Could you give it a try?

Thanks,
  Stefano

[0001-tests-avoid-spurious-failure-when-running-as-root.patch (text/x-diff, attachment)]

Message #47 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org,
	"a >> \"automake-patches <at> gnu.org\"" <automake-patches <at> gnu.org>
Subject: Re: bug#12041: Issues running the testsuite as root
Date: Wed, 25 Jul 2012 08:33:03 -0400

> The attached patch should solve the issue.  Could you give it a try?

Let's see if I applied that correctly : 

$ diff t/primary-prefix-couples-force-valid.sh_backup t/primary-prefix-couples-force-valid.sh
57c57,62
<       test ! -x '$(libexecdir)/bar.h'
---
> ## If this test is run as root, "test -x" could suceed also for
> ## non-executable files, so we need to protect the next check.
> ## See automake bug#12041.
>       if test -x Makefile; then echo SKIP THIS; else \
>         test ! -x '$(libexecdir)/bar.h'; \
>       fi;
$ 

looks good. 

If I su - then run the test I now see : 


bash-3.2# 
bash-3.2# id 
uid=0(root) gid=0(root) groups=1(other),2(bin),3(sys),4(adm),5(uucp),6(mail),7(tty),8(lp),9(nuucp),12(daemon)
bash-3.2# make check TESTS=t/primary-prefix-couples-force-valid AM_MAKEFLAGS='TESTS="$(TESTS)"'
make TESTS="t/primary-prefix-couples-force-valid" t/wrap/aclocal-1.12 t/wrap/automake-1.12 t/ax/test-init.sh   t/ax/plain-functions.sh   t/ax/tap-functions.sh \
  defs-static
`t/wrap/aclocal-1.12' is up to date.
`t/wrap/automake-1.12' is up to date.
`t/ax/test-init.sh' is up to date.
`t/ax/plain-functions.sh' is up to date.
`t/ax/tap-functions.sh' is up to date.
`defs-static' is up to date.
make TESTS="t/primary-prefix-couples-force-valid" check-TESTS check-local
PASS: t/primary-prefix-couples-force-valid.sh
============================================================================
Testsuite summary for GNU Automake 1.12.2
============================================================================
# TOTAL: 1
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================
bash-3.2# 


So that seems to fix that. 

However I am fairly certian that all files are not executable from the perspective
of the root user. That seems absurd. 

bash-3.2# id
uid=0(root) gid=0(root) groups=1(other),2(bin),3(sys),4(adm),5(uucp),6(mail),7(tty),8(lp),9(nuucp),12(daemon)

bash-3.2# ls -lap 
total 37
drwxr-xr-x   2 root     sys            7 Jul 25 12:29 ./
drwxr-xr-x  25 root     root          26 Jul 14 01:46 ../
-rwxr-xr-x   1 root     root          55 Jul 25 12:29 look.sh
-rwx------   1 root     root        1990 Jul 25 12:27 set.sh
-rwxr-xr-x   1 root     root        8600 Jul 25 12:27 x
-rw-r--r--   1 root     root         172 Jul 25 12:24 x.c
-rw-r--r--   1 root     root         285 Jul 25 12:25 y.c
bash-3.2# 
bash-3.2# cat look.sh
#!/bin/ksh

if test -x x.c; then
    echo "ta da"
fi 

bash-3.2# 
bash-3.2# ./look.sh 
bash-3.2# 


bash-3.2# vi thus.sh
#!/bin/ksh

if test -x look.sh; then
    echo "executable bit seen"
fi 

~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
"thus.sh" [New file]

bash-3.2# chmod 755 thus.sh 
bash-3.2# ./thus.sh 
executable bit seen


Dennis 

Message #50 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#12041: Issues running the testsuite as root
Date: Wed, 25 Jul 2012 15:20:10 +0200

On 07/25/2012 02:33 PM, Dennis Clarke wrote:
> 
> 
>> The attached patch should solve the issue.  Could you give it a try?
> 
> Seems to fix that. 
>
Good, I will soon apply it then.

> However I am fairly certian that all files are not executable from the
> perspective of the root user. That seems absurd.
>
That might well depend by the shell you are using maybe (ore more precisely,
in this case, the one that is selected by the configure running in the test
scripts).

Could you try what happens issuing this command as root with all the shells
you have at your disposal (/bin/sh, /usr/xpg4/bin/sh, /bin/ksh and bash at
least)?

    test -x /etc/passwd; echo $?

Anyway, the Autoconf manual reads:

    For historical reasons, Posix reluctantly allows implementations of
    'test -x' that will succeed for the root user, even if no execute
    permissions are present.

So my patch might be a good idea regardless of your use case, just as a
way to err on the side of safety.

Thanks,
  Stefano

Message #53 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Dennis Clarke <dclarke <at> blastwave.org>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 12041 <at> debbugs.gnu.org,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#12041: Issues running the testsuite as root
Date: Wed, 25 Jul 2012 09:26:31 -0400

> > 
> >> The attached patch should solve the issue.  Could you give it a try?
> > 
> > Seems to fix that. 
> >
> Good, I will soon apply it then.

  And by the way, thank you for truely awesome response speed and totally cool way that you just jump in a get things done. I think the open source world needs a lot more of guys like you. 

Me, I just break stuff and try to fix it :-) 

> > However I am fairly certian that all files are not executable from the
> > perspective of the root user. That seems absurd.
> >
> That might well depend by the shell you are using maybe (ore more precisely,
> in this case, the one that is selected by the configure running in the 
> test scripts).

I was thinking that too. I did run those tests with /bin/ksh as opposed to 
the bash shell. 

> Could you try what happens issuing this command as root with all the shells
> you have at your disposal (/bin/sh, /usr/xpg4/bin/sh, /bin/ksh and 
> bash at least)?

I'll see if I can find the enthusiasm for it ;-) 

>     test -x /etc/passwd; echo $?
> 
> Anyway, the Autoconf manual reads:
> 
>     For historical reasons, Posix reluctantly allows implementations of
>     'test -x' that will succeed for the root user, even if no execute
>     permissions are present.

wow. nice one there.  Who would have guessed. I could go dig in at the OpenGroup website and check on this but again, one has to ask "why?"

As far as I am concerned we have a test that passes as expected now regardless if one is root user ( stupidly ) or otherwise. All other tests seems to be fine. I say move on to other items.

> So my patch might be a good idea regardless of your use case, just as 
> a way to err on the side of safety.

I salute that thinking. 

Also, if you ever, for whatever reasons, want access to Solaris systems, just drop me a line with a public key and its done.

Dennis 

Message #56 received at 12041 <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041 <at> debbugs.gnu.org,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#12041: Issues running the testsuite as root
Date: Wed, 25 Jul 2012 15:39:19 +0200

On 07/25/2012 03:26 PM, Dennis Clarke wrote:
>
> Stefano Lattarini wrote:
>
>> Could you try what happens issuing this command as root with all the shells
>> you have at your disposal (/bin/sh, /usr/xpg4/bin/sh, /bin/ksh and 
>> bash at least)?
> 
> I'll see if I can find the enthusiasm for it ;-) 
>
Yeah, don't sweat it anyway; since the failure is solved, I'm already
satisfied, and as you say below, let's move on to other (better) items.

>> So my patch might be a good idea regardless of your use case, just as 
>> a way to err on the side of safety.
> 
> I salute that thinking. 
>
Glad of hearing that :-)

> Also, if you ever, for whatever reasons, want access to Solaris systems,
> just drop me a line with a public key and its done.
>
Thanks, but I already has access to such systems (which might explain why
you found so few failures in the testsuite on your Solaris ;-).  I couldn't
try this particular patch by myself because because I don't have root
privileges on those Solaris boxen access I have access to (nor I want it;
less risk of messing up things).

Thanks,
  Stefano

Message #61 received at 12041-done <at> debbugs.gnu.org (full text, mbox):

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Dennis Clarke <dclarke <at> blastwave.org>
Cc: 12041-done <at> debbugs.gnu.org,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>
Subject: Re: bug#12041: Issues running the testsuite as root
Date: Thu, 26 Jul 2012 19:33:36 +0200

On 07/25/2012 03:39 PM, Stefano Lattarini wrote:
> On 07/25/2012 03:26 PM, Dennis Clarke wrote:
>>
>> Stefano Lattarini wrote:
>>
>>> Could you try what happens issuing this command as root with all the shells
>>> you have at your disposal (/bin/sh, /usr/xpg4/bin/sh, /bin/ksh and 
>>> bash at least)?
>>
>> I'll see if I can find the enthusiasm for it ;-) 
>>
> Yeah, don't sweat it anyway; since the failure is solved, I'm already
> satisfied, and as you say below, let's move on to other (better) items.
>
BTW, I've finally pushed the patch, and I'm thus closing this bug report.

Thanks,
  Stefano

Previous Next

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