[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Testsuite failures on Tru64 OSF 5.1
From: |
Stefano Lattarini |
Subject: |
Re: Testsuite failures on Tru64 OSF 5.1 |
Date: |
Mon, 15 Nov 2010 23:57:14 +0100 |
User-agent: |
KMail/1.13.3 (Linux/2.6.30-2-686; KDE/4.4.4; i686; ; ) |
On Monday 15 November 2010, Ralf Wildenhues wrote:
> * Stefano Lattarini wrote on Sun, Nov 14, 2010 at 11:00:16PM CET:
> > <http://autobuild.josefsson.org/automake/log-201011141902490189000.txt>
>
> > > FAIL: backcompat5.test (exit: 1)
> > > ================================
> > >
> > [CUT]
> > > find ../foo-1.0 -print ## useful for debugging
> > > find: missing conjunction
> > > *** Exit 1
> > > Stop.
> > Seems like a limitation (bug) of the find utility; what I'd do is
> > replacing the above find command simply with:
> > find ../foo-1.0
> > WDYT?
>
> I think the comment is taken as part of the command.
Hmm... that's an automake comment: shouldn't automake strip it? But even
if it doesn't, shouldn't the comment in question be consired a shell
comment anyway? If that's not the case, well, I'd regard this behaviour
as a severe bug in the OSF make implementation.
> > > FAIL: instspc-*-build.test (exit: 1)
> > > FAIL: instspc-*-install.test (exit: 1)
> > Re-running the tests with `/bin/ksh -x' might really help here. No idea
> > what might have ben gone wrong otherwise. And yes, this is clearly a bug
> > introduced by my recent "instspc.test refactoring" patch.
>
> Not sure.
I'd say it is; see below.
> instspc.test was skipped on most of my test systems because I
> did not have gcc in $PATH (deliberately, but for other reasons).
>
> How come the verbose output didn't land in test-suite.log though?
A spurious failure coming early in `tests/instspc-tests.sh', before
`defs' is sourced, would not be logged, since the `xtrace' shell flag
is not yet set. So the failure is probably due to a bug/limitation
in `instspc-tests.sh' (and thus caused by recent "instspc.test
refactoring" patch, as stated above).
> Rest comes later.
OK.
Regards,
Stefano
- Re: Testsuite failures on Tru64 OSF 5.1, (continued)
- Re: Testsuite failures on Tru64 OSF 5.1, Ralf Wildenhues, 2010/11/15
- Re: Testsuite failures on Tru64 OSF 5.1, Peter Rosin, 2010/11/16
- Re: Testsuite failures on Tru64 OSF 5.1, Stefano Lattarini, 2010/11/16
- Re: Testsuite failures on Tru64 OSF 5.1, Peter Rosin, 2010/11/16
- Re: Testsuite failures on Tru64 OSF 5.1, Stefano Lattarini, 2010/11/16
- Re: Testsuite failures on Tru64 OSF 5.1, Stefano Lattarini, 2010/11/16
Re: Testsuite failures on Tru64 OSF 5.1, Ralf Wildenhues, 2010/11/15
- Re: Testsuite failures on Tru64 OSF 5.1,
Stefano Lattarini <=
- backcompat5.test: avoid '##'-style comments inside recipe commands. (was: Testsuite failures on Tru64 OSF 5.1), Ralf Wildenhues, 2010/11/16
- Shell comments in make rules (was: backcompat5.test: avoid '##'-style comments inside recipe commands), Stefano Lattarini, 2010/11/16
- Re: Shell comments in make rules (was: backcompat5.test: avoid '##'-style comments inside recipe commands), Ralf Wildenhues, 2010/11/16
- Re: Shell comments in make rules, Stefano Lattarini, 2010/11/16
- Re: Shell comments in make rules, Ralf Wildenhues, 2010/11/16
- Re: Shell comments in make rules, Stefano Lattarini, 2010/11/16
Spurious failures of some silent*.test tests when cc != gcc (was: Testsuite failures on Tru64 OSF 5.1), Stefano Lattarini, 2010/11/17
Testsuite failures on Solaris 2.10 on SPARC (was: testsuite results from master), Stefano Lattarini, 2010/11/14