automake-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[automake-commit] branch master updated: doc: mention overriding SUBDIRS


From: Karl Berry
Subject: [automake-commit] branch master updated: doc: mention overriding SUBDIRS= with TESTS= and recursive make.
Date: Sun, 22 Nov 2020 13:13:27 -0500

This is an automated email from the git hooks/post-receive script.

karl pushed a commit to branch master
in repository automake.

View the commit online:
https://git.savannah.gnu.org/gitweb/?p=automake.git;a=commitdiff;h=dd616e2dd21943486580ebc0e235aac2bb48b834

The following commit(s) were added to refs/heads/master by this push:
     new dd616e2  doc: mention overriding SUBDIRS= with TESTS= and recursive 
make.
dd616e2 is described below

commit dd616e2dd21943486580ebc0e235aac2bb48b834
Author: Karl Berry <karl@freefriends.org>
AuthorDate: Sun Nov 22 10:13:16 2020 -0800

    doc: mention overriding SUBDIRS= with TESTS= and recursive make.
    
    This change palliates https://bugs.gnu.org/42883,
    though it's not a real fix.
    
    * doc/automake.texi (Parallel Test Harness): with recursive
    make, when limiting the tests run, also presumably needed to
    override SUBDIRS.
---
 doc/automake.texi | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/doc/automake.texi b/doc/automake.texi
index 17bc2da..177bd66 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -9372,7 +9372,19 @@ command like this to run only a subset of the tests:
 env TESTS="foo.test bar.test" make -e check
 @end example
 
-Note however that the command above will unconditionally overwrite the
+@c https://bugs.gnu.org/42883
+If you're using a recursive make setup, you'll probably also need to
+override @code{SUBDIRS}:
+
+@example
+env TESTS="foo.test bar.test" make -e check SUBDIRS=
+@end example
+
+Otherwise, the test harness will descend into all subdirectories,
+where the tests presumably do not exist, and thus fail.  (Patch to
+provide better behavior would be welcome.)
+
+Another issue: the command above will unconditionally overwrite the
 @file{test-suite.log} file, thus clobbering the recorded results
 of any previous testsuite run.  This might be undesirable for packages
 whose testsuite takes a long time to execute.  Luckily, this problem can



reply via email to

[Prev in Thread] Current Thread [Next in Thread]