Re: Testsuite failures on Tru64 OSF 5.1

Den 2010-11-15 23:23 skrev Ralf Wildenhues: > Hi Peter, > > * Peter Rosin wrote on Mon, Nov 15, 2010 at 09:19:44AM CET: >> This is based off of master (but I guess it also applies to tests-init) >> but the backport to the msvc branch is trivial. I "stole" the xsi-test >> from libtool. >> >> Would

Re: [PATCH] {maint} Improve and extend tests on de-ansification support.

On Monday 15 November 2010, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Mon, Nov 15, 2010 at 02:37:13AM CET: > > On Sunday 14 November 2010, Ralf Wildenhues wrote: > > > * Stefano Lattarini wrote on Mon, Sep 13, 2010 at 10:59:22AM CEST: > > > > But since we are at it, we can do better, ex

Re: Testsuite failures on Tru64 OSF 5.1

On Monday 15 November 2010, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Sun, Nov 14, 2010 at 11:00:16PM CET: > > > > > > FAIL: backcompat5.test (exit: 1) > > > > > > > > [CUT] > > >

Re: Testsuite failures on AIX 5.3

On Monday 15 November 2010, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Sun, Nov 14, 2010 at 10:14:54PM CET: > > > > > + /bin/grep -F -v @SET_MAKE@ Makefile.in > > > + 1> Makefile.sed > > > + make -f Makefile.sed

Re: Testsuite failures on Tru64 OSF 5.1

* Stefano Lattarini wrote on Sun, Nov 14, 2010 at 11:00:16PM CET: > > > FAIL: backcompat5.test (exit: 1) > > > > > [CUT] > > find ../foo-1.0 -print ## useful for debugging > > find: missing co

Re: Testsuite failures on Tru64 OSF 5.1

Hi Peter, * Peter Rosin wrote on Mon, Nov 15, 2010 at 09:19:44AM CET: > This is based off of master (but I guess it also applies to tests-init) > but the backport to the msvc branch is trivial. I "stole" the xsi-test > from libtool. > > Would be good if someone tested on that Alpha before pushing

Re: [PATCH] {maint} Improve and extend tests on de-ansification support.

* Stefano Lattarini wrote on Mon, Nov 15, 2010 at 02:37:13AM CET: > On Sunday 14 November 2010, Ralf Wildenhues wrote: > > * Stefano Lattarini wrote on Mon, Sep 13, 2010 at 10:59:22AM CEST: > > > But since we are at it, we can do better, extending coverage and > > > making existing tests more "sem

Re: Testsuite failures on AIX 5.3

* Stefano Lattarini wrote on Sun, Nov 14, 2010 at 10:14:54PM CET: > > > + /bin/grep -F -v @SET_MAKE@ Makefile.in > > + 1> Makefile.sed > > + make -f Makefile.sed SHELL=/bin/sh test1 > > echo ' @top_srcdir@/configure.

[PATCH 0/5] More patches for the tests-init branch

Stefano Lattarini (5): Tests defs: don't let useless variables leak in test scripts. Tests defs: new subroutine `skip' for test skipping. Tests defs: some cleanup and minor fixes. Tests defs: avoid some useless subshells. Tests required tools: also try `-v' option for GNU compilers. No "

[PATCH 1/5] Tests defs: don't let useless variables leak in test scripts.

* tests/defs ($priv_check_temp, $overwrite_status, $ro_dir_temp, $create_status, $r2h, $libtool_found, $gettext_found, $aclocaldir, $extra_includes): Unset once they've served their purpose. --- ChangeLog |7 +++ tests/defs |5 + 2 files changed, 12 insertions(+), 0 deletions(-) F

[PATCH 2/5] Tests defs: new subroutine `skip' for test skipping.

Tests defs: new subroutine `skip' for test skipping. * tests/defs.in (skip): New subroutine, causing the running test script to be SKIP'd, possibly with a meaningful message. Use it throughout. * tests/REAMDE: Updated. * tests/color.test: Use the new `skip' subroutine. * tests/color2.test: Likewis

[PATCH 3/5] Tests defs: some cleanup and minor fixes.

* tests/defs: Exit with status 99 (hard error) rather than 1 (failure) on unexpected/internal errors, or when a signal is caught by the client script. Some minor changes in spacing and formatting. ($extra_includes): Variable renamed to ... ($acincludes): ... this one, and extended. --- ChangeLog

[PATCH 4/5] Tests defs: avoid some useless subshells.

* tests/defs: In the loop on "$required" tools: avoid subshells where not neded. --- ChangeLog |4 tests/defs | 30 +++--- 2 files changed, 19 insertions(+), 15 deletions(-) From ccf42890cb5a5cc89e62593987f9a1b7c3895480 Mon Sep 17 00:00:00 2001 From: Stefano Lat

[PATCH 5/5] Tests required tools: also try `-v' option for GNU compilers.

* tests/defs.in: In the loop on "$required" tools, for gcc and g++, also run "gcc -v" (resp. "g++ -v"), to get more information, and for consistency with gcj. --- ChangeLog |5 + tests/defs |4 2 files changed, 9 insertions(+), 0 deletions(-) From d487ed740f47a9ec82bb8b99d886e2a

Re: tests: work around dash quoting issue in case statements.

On 11/14/2010 10:24 AM, Ralf Wildenhues wrote: > tests: work around dash quoting issue in case statements. > > * tests/color.test, tests/color2.test: Quote variable in case > pattern, to avoid skipping tests with dash 0.5.5.1. > > diff --git a/tests/color.test b/tests/color.test >

Re: [PATCH] tests/yaccdry.test ($required): Require bison.

On Monday 15 November 2010, Stefano Lattarini wrote: > I'm seeing this failure in test yaccdry.test at the Hydra continuous > build system for automake: > > [CUT] > > OK to apply the attached patch to a temporary bugfix branch to be > then merged into maint? Please disregard this message. The bu

Re: [PATCH] compile: clear the `eat' variable earlier.

On Monday 15 November 2010, Peter Rosin wrote: > Den 2010-11-15 11:44 skrev Stefano Lattarini: > >> Should I fixup the ChangeLog entry? > > I'd say just to merge the "update scriptversion" message with the > > previous entry in the ChangeLog, like this: > > > > +2010-11-15 Peter Rosin > > + > >

Re: [PATCH] compile: clear the `eat' variable earlier.

Den 2010-11-15 11:44 skrev Stefano Lattarini: >> Should I fixup the ChangeLog entry? > I'd say just to merge the "update scriptversion" message with the > previous entry in the ChangeLog, like this: > > +2010-11-15 Peter Rosin > + > + compile: clear the `eat' variable earlier. > + *

Re: [PATCH] compile: clear the `eat' variable earlier.

On Monday 15 November 2010, Peter Rosin wrote: > Den 2010-11-15 10:40 skrev Peter Rosin: > > Den 2010-11-15 10:33 skrev Peter Rosin: > >> Hi! > >> > >> I found this little gem in compile while reading the code. Pushed as > >> obvious to the msvc branch. > > > > Obviously I tripped up while commit

Re: Testsuite failures on Tru64 OSF 5.1

On Monday 15 November 2010, Peter Rosin wrote: > Den 2010-11-15 09:19 skrev Peter Rosin: > > diff --git a/tests/defs b/tests/defs > > index 82c3b5b..e37bb96 100644 > > --- a/tests/defs > > +++ b/tests/defs > > @@ -290,6 +290,15 @@ do > >echo "$me: running texi2dvi -o /dev/null --version" >

Re: [PATCH] compile: clear the `eat' variable earlier.

Den 2010-11-15 10:40 skrev Peter Rosin: > Den 2010-11-15 10:33 skrev Peter Rosin: >> Hi! >> >> I found this little gem in compile while reading the code. Pushed as >> obvious to the msvc branch. > > Obviously I tripped up while committing something obvious. Sorry for > being sloppy. So, I also

Re: [PATCH] compile: clear the `eat' variable earlier.

Den 2010-11-15 10:33 skrev Peter Rosin: > Hi! > > I found this little gem in compile while reading the code. Pushed as > obvious to the msvc branch. Obviously I tripped up while committing something obvious. Sorry for being sloppy. So, I also pushed this follow-up commit to the msvc branch: C

[PATCH] compile: clear the `eat' variable earlier.

Hi! I found this little gem in compile while reading the code. Pushed as obvious to the msvc branch. Cheers, Peter >From 89bf665808e6ed7a68957342e6343cf3261ebf14 Mon Sep 17 00:00:00 2001 From: Peter Rosin Date: Mon, 15 Nov 2010 10:27:55 +0100 Subject: [PATCH] compile: clear the `eat' variable

Re: Testsuite failures on Tru64 OSF 5.1

Den 2010-11-15 09:19 skrev Peter Rosin: > diff --git a/tests/defs b/tests/defs > index 82c3b5b..e37bb96 100644 > --- a/tests/defs > +++ b/tests/defs > @@ -290,6 +290,15 @@ do >echo "$me: running texi2dvi -o /dev/null --version" >( texi2dvi -o /dev/null --version ) || exit 77 >

Re: Testsuite failures on Tru64 OSF 5.1

Den 2010-11-15 01:39 skrev Stefano Lattarini: > On Monday 15 November 2010, Peter Rosin wrote: >> Running MSVC on osfX.Y is not interesting. I'd write a patch to skip >> the test > Yeah, I agree this is the best option. >> but I can't then test the result. > Me neither (I don't have access to a Tr