summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorPádraig Brady <P@draigBrady.com>2009-02-12 13:51:03 +0000
committerPádraig Brady <P@draigBrady.com>2009-02-13 11:13:33 +0000
commit48cae1e8642684f0103848b84d5884d1ba2412c8 (patch)
tree1845ae20d9e6f76bc906f7291fa91f33b4b1a656 /README
parent022889a4575390b656abf89b0e8f43ef03c1cc00 (diff)
downloadcoreutils-48cae1e8642684f0103848b84d5884d1ba2412c8.tar.gz
maint: mention how to run a single test in HACKING docs
* HACKING: Give an example of how to run a test in isolation. * README: Fix/simplify example for running a single test. * README-hacking: Reference the HACKING file.
Diffstat (limited to 'README')
-rw-r--r--README14
1 files changed, 5 insertions, 9 deletions
diff --git a/README b/README
index 157432ec6..58aec019c 100644
--- a/README
+++ b/README
@@ -161,17 +161,13 @@ Reporting bugs:
IMPORTANT: if you take the time to report a test failure,
please be sure to include the output of running `make check'
in verbose mode for each failing test. For example,
-if the test that fails is tests/mv/hard-link-1, then you
-would run this command:
+if the test that fails is tests/misc/df, then you would
+run this command:
- env VERBOSE=yes make check -C tests/mv TESTS=hard-link-1 >> log 2>&1
+ (cd tests && make check TESTS=misc/df VERBOSE=yes) >> log 2>&1
-For some tests, you can get even more detail by including
-DEBUG=yes in the environment:
-
- env DEBUG=yes VERBOSE=yes make check -C tests/mv TESTS=hard-link-1 >> log 2>&1
-
-and then include the contents of the file `log' in your bug report.
+For some tests, you can get even more detail by adding DEBUG=yes.
+Then include the contents of the file `log' in your bug report.
***************************************