On Sunday 14 November 2010, Ralf Wildenhues wrote: > Hello Stefano, > > I think it is time to reevaluate some of the work that has been done in > the last few weeks. I'd like to ask you to postpone pushes of pending > stuff that has a clock ticking, and look at the lots of new failures > that a testsuite run shows on a few hosts; you can find them in some > minutes on <http://autobuild.josefsson.org/automake/>. >
Log: <http://autobuild.josefsson.org/automake/log-201011141903352512000.txt> Minimal system information: configure: autobuild project... GNU Automake configure: autobuild revision... v1.11-225-gcdd3cf3 configure: autobuild hostname... ichigo configure: autobuild mode... default configure: autobuild timestamp... 20111412T185841Z CONFIG_SHELL=/bin/sh /bin/sh ../automake/configure checking build system type... hppa2.0w-hp-hpux11.23 -*-*-*- > FAIL: instspc-space-build.test (exit: 1) > FAIL: instspc-space-install.test (exit: 1) > FAIL: instspc-tab-build.test (exit: 1) > FAIL: instspc-tab-install.test (exit: 1) Hmpf. Not very nice. Apparently, the whitespaces got eaten somehow in the make rules: > ../install-sh -c -d > '/tmp/am/build-hppa2.0w-hp-hpux11.23/tests/instspc-space-build.dir/sub1/ > -prefix/foo/sub' OK, space is there ... > ../install-sh -c -m 644 ../sub/nobase.h > '/tmp/am/build-hppa2.0w-hp-hpux11.23/tests/instspc-space-build.dir/sub1/ > -prefix/foo/sub' ... and here ... > test -f > '/tmp/am/build-hppa2.0w-hp-hpux11.23/tests/instspc-space-build.dir/sub1/-prefix/foo/sub/nobase.h' ... but not here! > *** Error exit code 1 And failure ensues. My knee-jerk guess is that the (leading?) whitespaces got stripped from the variable `file' even if it's defined from the command line: DESTDIR="$dest" file="$instspc_test_string" $MAKE -e test-install-sep Is this guess correct? Is this a known limitation/bug of HP-UX make? Is it worth working around? (e.g. by adding some more sanity checks and skipping the test if they fail) > FAIL: instspc-formfeed-build.test (exit: 1) > FAIL: instspc-formfeed-install.test (exit: 1) > FAIL: instspc-carriageret-build.test (exit: 1) > FAIL: instspc-carriageret-install.test (exit: 1) On the other hand, I wouldn't care about these failures. Getting to the point: how was the older `instspc.test' behaving on this system? Without knowing that, it's hard to tell if we've introduced a regression, or are just hitting known bugs/limits of HP-UX. -*-*-*- > FAIL: parallel-tests.test (exit: 1) Not caused by recent testsuite work (and I can't easily guess why it's failing). > FAIL: spy.test (exit: 1) This is not really a test on automake/aclocal, but a "spy" test on the make implementation available, to see if double-colon rules work for it. The heading comments read: # Check whether double colon rules work. The Unix V7 make manual # mentions double-colon rules, but POSIX does not. They seem to be # supported by all Make implementation as we can tell. This test case # is a spy: we want to detect if there exist implementations where # these do not work. We might use these rules to simplify the rebuild # rules (instead of the $? hack). But currently automake doesn't use double-colon rules in the generated makefiles, so no big deal IMHO. -*-*-*- FAIL: distlinksbrk.test (exit: 1) ================================= > /tmp/am/build-hppa2.0w-hp-hpux11.23/tests:/tmp/local/hppa2.0w-hp-hpux11.23/bin > :/tmp/bin:/opt/aCC/bin:/opt/ansic/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/X11 > :/usr/ccs/bin:/usr/contrib/bin/X11:/usr/vue/bin:/opt/imake/bin > + pwd > /tmp/am/build-hppa2.0w-hp-hpux11.23/tests/distlinksbrk.dir > + set -e > + lnk_base=BrknSymlnk > + lnk1=BrknSymlnk__001 > + lnk2=BrknSymlnk__002 > + lnka=BrknSymlnk__aaa > + lnkb=BrknSymlnk__bbb > + ln -s nonesuch BrknSymlnk__001 > + pwd > + ln -s /tmp/am/build-hppa2.0w-hp-hpux11.23/tests/distlinksbrk.dir/nonesuch > BrknSymlnk__002 > + ln -s BrknSymlnk__001 BrknSymlnk__aaa > + ln -s BrknSymlnk__aaa BrknSymlnk__bbb > + test ! -r BrknSymlnk__001 > + test ! -r BrknSymlnk__002 > + test ! -r BrknSymlnk__aaa > + test ! -r BrknSymlnk__bbb > + test -h BrknSymlnk__001 > + test -h BrknSymlnk__002 > + test -h BrknSymlnk__aaa > + test -h BrknSymlnk__bbb > + cat > + 1>> configure.in 0< /var/tmp/sh13163.8 > + cat > + 1> Makefile.am 0<< > EXTRA_DIST = BrknSymlnk__001 BrknSymlnk__002 BrknSymlnk__aaa BrknSymlnk__bbb > + ls -l > total 18 > lrwxrwxr-x 1 rwild rwild 8 Nov 12 20:16 BrknSymlnk__001 -> > nonesuch > lrwxrwxr-x 1 rwild rwild 74 Nov 12 20:16 BrknSymlnk__002 -> > /tmp/am/build-hppa2.0w-hp-hpux11.23/tests/distlinksbrk.dir/nonesuch > lrwxrwxr-x 1 rwild rwild 15 Nov 12 20:16 BrknSymlnk__aaa -> > BrknSymlnk__001 > lrwxrwxr-x 1 rwild rwild 15 Nov 12 20:16 BrknSymlnk__bbb -> > BrknSymlnk__aaa > -rw-rw-r-- 1 rwild rwild 77 Nov 12 20:16 Makefile.am > -rw-rw-r-- 1 rwild rwild 86 Nov 12 20:16 configure.in > -rwxr-xr-x 1 rwild rwild 20001 Nov 12 20:16 depcomp > -rwxr-xr-x 1 rwild rwild 13781 Nov 12 20:16 install-sh > -rwxr-xr-x 1 rwild rwild 11419 Nov 12 20:16 missing > + aclocal-1.11a -Werror > + autoconf > + automake-1.11a --foreign -Werror -Wall > + ./configure > 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... no > checking for awk... awk > checking whether make sets $(MAKE)... yes > checking that generated files are newer than configure... done > configure: creating ./config.status > config.status: creating Makefile > + make distdir > No suffix list. ?!? What is this? > Make: Don't know how to make BrknSymlnk__001. Stop. > + make -k distdir > + 1> out 2>& 1 > + : > + cat out > No suffix list. > Make: Don't know how to make BrknSymlnk__001. Stop. Just an error message instead of four? Might this be a "make -k" bug? If yes, how does the attached test script fare? > + /bin/grep -F BrknSymlnk__001 out > Make: Don't know how to make BrknSymlnk__001. Stop. > + /bin/grep -F BrknSymlnk__002 out > + exit_status=1 > + set +e > + cd /tmp/am/build-hppa2.0w-hp-hpux11.23/tests > + test 0 != 0 > + echo distlinksbrk: exit 1 > distlinksbrk: exit 1 > + exit 1 -*-*-*- Regards, Stefano
distlinksbrk2.test
Description: application/shellscript