[PATCH] testsuite: make test logs more verbose

Stefano Lattarini <[email protected]>
Newsgroups gmane.comp.gnu.utils.bugs
Message-ID <82765e693e4f3d248e471084a1a4e0e89cf2704a.1356807118.git.stefano.lattarini@gmail.com>
The Automake-provided parallel testsuite harness take care of
redirection the stdout and stderr of the run test cases to a
corresponding log file, so we no longer have to worry about
avoiding to pollute the "make test" output.

* testsuite/runtest: Adjust and simplify.

Copyright-paperwork-exempt: yes
Signed-off-by: Stefano Lattarini <[email protected]>
---
 ChangeLog         |    5 +++++
 testsuite/runtest |   17 ++++-------------
 2 files changed, 9 insertions(+), 13 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index a368c87..2db5575 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2012-12-29  Stefano Lattarini  <[email protected]>  (tiny change)
 
+	testsuite: make test logs more verbose
+	* testsuite/runtest: Adjust and simplify.
+
+2012-12-29  Stefano Lattarini  <[email protected]>  (tiny change)
+
 	bootstrap: avoid yet another spurious failure
 	* bootstrap: The 'missing' script has been dropped from the
 	Gnulib repository; don't check for it to be present then.
diff --git a/testsuite/runtest b/testsuite/runtest
index 80ce903..4983312 100755
--- a/testsuite/runtest
+++ b/testsuite/runtest
@@ -7,17 +7,8 @@
 makefile="$srcdir/Makefile.tests"
 test=`echo "$@"| sed 's,.*/,,'`
 
-# As a convenience, suppress the output of make if the test passes
-if $MAKE SED="$SED" srcdir="$srcdir" -f "$makefile" $test > $test.test 2>&1; then
-  exitcode=0
-  rm -f $test.test
-else
-  exitcode=$?
-fi
-if test -f $test.skip; then
-  exitcode=77
-else
-  test -f $test.test && cat $test.test
-fi
-rm -f $test.test $test.skip
+exitcode=0
+$MAKE SED="$SED" srcdir="$srcdir" -f "$makefile" $test || exitcode=$?
+test -f $test.skip && exitcode=77
+rm -f $test.skip
 exit $exitcode
-- 
1.7.10.4
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.