[PATCH 4/6] Update VERBOSE handling for parallel-tests driver.

[Ralf Wildenhues]

* tests/defs.m4sh: Default to verbose output, drop now-unneeded
handling of 'VERBOSE=no'.
* README: Update example usage.
* README.alpha: Likewise.
* doc/libtool.texi (Test descriptions, When tests fail): Remove
unneeded VERBOSE recommendations.  Point to per-test log files
and test-suite.log summary file.

Signed-off-by: Ralf Wildenhues <address@hidden>
---
 ChangeLog        |    9 +++++++++
 README           |   14 +++++---------
 README.alpha     |   14 +++++---------
 doc/libtool.texi |   14 +++++---------
 tests/defs.m4sh  |    9 ++-------
 5 files changed, 26 insertions(+), 34 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index a1b2d07..0363756 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,14 @@
 2010-08-22  Ralf Wildenhues  <address@hidden>
 
+       Update VERBOSE handling for parallel-tests driver.
+       * tests/defs.m4sh: Default to verbose output, drop now-unneeded
+       handling of 'VERBOSE=no'.
+       * README: Update example usage.
+       * README.alpha: Likewise.
+       * doc/libtool.texi (Test descriptions, When tests fail): Remove
+       unneeded VERBOSE recommendations.  Point to per-test log files
+       and test-suite.log summary file.
+
        Enable parallel-tests test driver for the old testsuite.
        * configure.ac: New configure test to find out whether `make'
        supports order-only prerequisites; set @ORDER@ accordingly.
diff --git a/README b/README
index 0a9317f..44396dc 100644
--- a/README
+++ b/README
@@ -76,15 +76,11 @@ If you wish to report a test group failure to the libtool 
list, you need
 to send the verbose output of the FAILing group, along with the
 information from the end of `$(top_builddir)/libtool --help' to the bug
 report mailing list, <address@hidden> with a subject line that
-includes the string `[TEST FAILURE]'.  From a Bourne compatible shell,
-you can generate verbose test output like this:
+includes the string `[TEST FAILURE]'.  The file test-suite.log contains
+the verbose output from all failed tests.
 
-  VERBOSE=yes gmake check \
-  TESTS="tests/cdemo-static.test tests/cdemo-make.test tests/cdemo-exec.test" \
-  TESTSUITEFLAGS=-V | tee cdemo-static-group.log
-
-In order to enable debug shell tracing, use VERBOSE=debug instead of
-VERBOSE=yes.
+In order to enable debug shell tracing, you can set VERBOSE=debug when
+running the old test suite.
 
 
 In the long run, Libtool will move to using only the new,
@@ -174,7 +170,7 @@ For more details about version numbers, see:
     http://www.gnu.org/software/libtool/contribute.html
 
 -- 
-  Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009  Free Software
+  Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software
   Foundation, Inc.
   Written by Gary V. Vaughan, 2004
 
diff --git a/README.alpha b/README.alpha
index a785a7b..ca92329 100644
--- a/README.alpha
+++ b/README.alpha
@@ -81,15 +81,11 @@ If you wish to report a test group failure to the libtool 
list, you need
 to send the verbose output of the FAILing group, along with the
 information from the end of `$(top_builddir)/libtool --help' to the bug
 report mailing list, <address@hidden> with a subject line that
-includes the string `[TEST FAILURE]'.  From a Bourne compatible shell,
-you can generate verbose test output like this:
+includes the string `[TEST FAILURE]'.  The file test-suite.log contains
+the verbose output from all failed tests.
 
-  VERBOSE=yes gmake check \
-  TESTS="tests/cdemo-static.test tests/cdemo-make.test tests/cdemo-exec.test" \
-  TESTSUITEFLAGS=-V | tee cdemo-static-group.log
-
-In order to enable debug shell tracing, use VERBOSE=debug instead of
-VERBOSE=yes.
+In order to enable debug shell tracing, you can set VERBOSE=debug when
+running the old test suite.
 
 
 In the long run, Libtool will move to using only the new,
@@ -114,7 +110,7 @@ send the file `tests/testsuite.log' to the bug report 
mailing list,
 <address@hidden>.
 
 -- 
-  Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009  Free Software
+  Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software
   Foundation, Inc.
   Written by Gary V. Vaughan, 2004
 
diff --git a/doc/libtool.texi b/doc/libtool.texi
index d0eaec4..bf51157 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -5121,8 +5121,8 @@ correspond to libtool's own notion of how your linker 
behaves.
 @pindex demo-relink.test
 @pindex depdemo-relink.test
 These tests check whether variable @code{shlibpath_overrides_runpath} is
-properly set.  If the test fails and @env{VERBOSE} is set, it will
-indicate what the variable should have been set to.
+properly set.  If the test fails, it will indicate what the variable should
+have been set to.
 
 @item demo-noinst-link.test
 @pindex demo-noinst-link.test
@@ -5396,8 +5396,9 @@ test suite.
 @cindex failed tests
 @cindex tests, failed
 
-Each of the tests in the old test suite are designed to produce no
-output when they are run via @kbd{make check}.  The exit status of each
+When the tests in the old test suite are run via @command{make check},
+output is caught in per-test @file{tests/@var{test-name}.log} files
+and summarized in the @file{test-suite.log} file.  The exit status of each
 program tells the @file{Makefile} whether or not the test succeeded.
 
 If a test fails, it means that there is either a programming error in
@@ -5407,11 +5408,6 @@ To investigate a particular test, you may run it 
directly, as you would
 a normal program.  When the test is invoked in this way, it produces
 output that may be useful in determining what the problem is.
 
-Another way to have the test programs produce output is to set the
address@hidden environment variable to @samp{yes} before running them.
-For example, @kbd{env VERBOSE=yes make check} runs all the tests, and
-has each of them display debugging information.
-
 The new, Autotest-based test suite produces as output a file
 @file{tests/testsuite.log} which contains information about failed
 tests.
diff --git a/tests/defs.m4sh b/tests/defs.m4sh
index 50fce10..8ffde5b 100644
--- a/tests/defs.m4sh
+++ b/tests/defs.m4sh
@@ -43,15 +43,10 @@ if test -z "$DJGPP"; then
     CONFIG_SITE=/nonexistent
 fi
 
-# How verbose should we be?  Default is no test output.
-# Setting VERBOSE=yes enables test output.
-# Setting VERBOSE=debug also puts the shell in debug mode.
+# How verbose should we be?  Default is test output in log file.
+# Setting VERBOSE=debug puts the shell in debug mode.
 opt_debug=:
-test "${VERBOSE+set}" != "set" && VERBOSE=no
 case "$VERBOSE" in
-NO | no | 0 | "")
-  exec > /dev/null 2>&1
-  ;;
 DEBUG | debug )
   opt_debug='set -x'
   $opt_debug
-- 
1.7.2.1.222.g9988