This is the mail archive of the
mailing list for the GDB project.
Re: RFC: parallelize "make check"
- From: Tom Tromey <tromey at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 25 Jun 2009 14:21:43 -0600
- Subject: Re: RFC: parallelize "make check"
- References: <firstname.lastname@example.org> <email@example.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Eli" == Eli Zaretskii <firstname.lastname@example.org> writes:
Eli> It would be good to mention this possibility in README, IMO.
2009-06-25 Tom Tromey <email@example.com>
* README: Mention parallel check.
diff --git a/gdb/README b/gdb/README
index 7116227..7feff8a 100644
@@ -646,6 +646,15 @@ The last method gives you slightly more control in case of problems
with building one or more test executables or if you are using the
testsuite `standalone', without it being part of the GDB source tree.
+The first two methods will let you run different parts of the
+testsuite in parallel, if you use GNU make and its `-j' option. In
+this case, if you set `RUNTESTFLAGS' then, by default, the tests will
+be run serially. You can override this and force a parallel run by
+setting the `make' variable `FORCE_PARALLEL' to any non-empty value.
+Note that the parallel `make check' assumes that you want to run the
+entire testsuite, so it is not compatible with some dejagnu options,
See the DejaGNU documentation for further details.