Re: Document INNER_TESTSUITEFLAGS, drop leading space

2009-03-03 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Sat, Feb 28, 2009 at 05:14:43PM CET:
 I found this very helpful while debugging the template test inside the
 low max_cmd_len test.  Any reasons against applying it?

Pushed.

Cheers,
Ralf

 2009-02-28  Ralf Wildenhues  ralf.wildenh...@gmx.de
 
   Document INNER_TESTSUITEFLAGS, drop leading space.
   * README: Document INNER_TESTSUITEFLAGS.
   * tests/cmdline_wrap.at (Run tests with low max_cmd_len):
   When using INNER_TESTSUITEFLAGS on the testsuite invocation,
   drop leading space after -k libtool, so that the user may
   further limit the set of tests to be run.




Document INNER_TESTSUITEFLAGS, drop leading space

2009-02-28 Thread Ralf Wildenhues
Hello,

I found this very helpful while debugging the template test inside the
low max_cmd_len test.  Any reasons against applying it?

Thanks,
Ralf

2009-02-28  Ralf Wildenhues  ralf.wildenh...@gmx.de

Document INNER_TESTSUITEFLAGS, drop leading space.
* README: Document INNER_TESTSUITEFLAGS.
* tests/cmdline_wrap.at (Run tests with low max_cmd_len):
When using INNER_TESTSUITEFLAGS on the testsuite invocation,
drop leading space after -k libtool, so that the user may
further limit the set of tests to be run.

diff --git a/README b/README
index 2bffd27..612699e 100644
--- a/README
+++ b/README
@@ -104,6 +104,15 @@ possible to test an installed script, possibly from a 
different Libtool
 release, with
   gmake check-local TESTSUITEFLAGS=-k libtool LIBTOOL=/path/to/libtool
 
+Some tests, like the one exercising max_cmd_len limits, make use of this
+to invoke the testsuite recursively on a subset of tests.  For these
+tests, the variable INNER_TESTSUITEFLAGS may be used.  It will be
+expanded right after the `-k libtool', without separating whitespace,
+so that further limiting of the recursive set of tests is possible.
+For example, to run only the template tests within the max_cmd_len, use
+  gmake check-local TESTSUITEFLAGS=-v -x -k max_cmd_len \
+ INNER_TESTSUITEFLAGS=',template -v -x'
+
 If you wish to report test failures to the libtool list, you need to
 send the file `tests/testsuite.log' to the bug report mailing list,
 bug-libt...@gnu.org.
@@ -165,7 +174,8 @@ For more details about version numbers, see:
 http://www.gnu.org/software/libtool/contribute.html
 
 -- 
-  Copyright (C) 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
+  Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009  Free Software
+  Foundation, Inc.
   Written by Gary V. Vaughan, 2004
 
   This file is part of GNU Libtool.
diff --git a/tests/cmdline_wrap.at b/tests/cmdline_wrap.at
index 0c47db8..13edabc 100644
--- a/tests/cmdline_wrap.at
+++ b/tests/cmdline_wrap.at
@@ -1,6 +1,6 @@
 # cmdline_wrap.at -- run tests with low max_cmd_len   -*- Autotest -*-
 
-#   Copyright (C) 2007 Free Software Foundation, Inc.
+#   Copyright (C) 2007, 2009 Free Software Foundation, Inc.
 #   Written by Ralf Wildenhues, 2007
 #
 #   This file is part of GNU Libtool.
@@ -40,7 +40,7 @@ mkdir tests
 cd tests
 INNER_TESTSUITEFLAGS=$INNER_TESTSUITEFLAGS abs_top_srcdir=$abs_top_srcdir \
   abs_builddir=$abs_builddir
-AT_CHECK([$CONFIG_SHELL $abs_srcdir/testsuite -k libtool 
$INNER_TESTSUITEFLAGS],
+AT_CHECK([$CONFIG_SHELL $abs_srcdir/testsuite -k libtool$INNER_TESTSUITEFLAGS],
 [], [ignore], [ignore])
 
 AT_CLEANUP