[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Changes to m4/README,v
From: |
Eric Blake |
Subject: |
Changes to m4/README,v |
Date: |
Mon, 19 Jun 2006 13:03:56 +0000 |
CVSROOT: /sources/m4
Module name: m4
Changes by: Eric Blake <ericb> 06/06/19 13:03:55
Index: README
===================================================================
RCS file: /sources/m4/m4/README,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- README 10 Jun 2006 21:23:30 -0000 1.9
+++ README 19 Jun 2006 13:03:55 -0000 1.10
@@ -56,6 +56,18 @@
infer. Don't forget all relevant information about your operating
system, compiler, libraries, ...
+The easiest way to remember this information is by using the
+testsuite. Any test failures are automatically logged, along with
+lots of useful information about your setup; simply mailing
+tests/testsuite.log to address@hidden' is a good start. If you want
+to dive in and debug a failure, you may find it useful to fine-tune
+the execution of the testsuite. For example, running test 12 in
+verbose mode can be done with:
+
+make check TESTSUITEFLAGS='-v -d -x 12'
+
+The testsuite understands --help to tell you more about the current
+set of tests.
## ------- ##