From: Nicholas Clark <nick@ccl4.org>
Date: Wed, 24 Jun 2009 16:20:15 +0000 (+0100)
Subject: Mention parallel testing in INSTALL and perl5110delta.pod
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=5ee651a9b9216a117835eca06b01232a8e3ac4a1;p=p5sagit%2Fp5-mst-13.2.git

Mention parallel testing in INSTALL and perl5110delta.pod
---

diff --git a/INSTALL b/INSTALL
index 147acd2..d2f072f 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1945,6 +1945,18 @@ about the various security aspects of temporary files.
 
 =back
 
+The core distribution can now run its regression tests in parallel on
+Unix-like platforms. Instead of running C<make test>, set C<TEST_JOBS> in
+your environment to the number of tests to run in parallel, and run
+C<make test_harness>. On a Bourne-like shell, this can be done as
+
+    TEST_JOBS=3 make test_harness  # Run 3 tests in parallel
+
+An environment variable is used, rather than parallel make itself, because
+L<TAP::Harness> needs to be able to schedule individual non-conflicting test
+scripts itself, and there is no standard interface to C<make> utilities to
+interact with their job schedulers.
+
 =head1 make install
 
 This will put perl into the public directory you specified to
diff --git a/pod/perl5110delta.pod b/pod/perl5110delta.pod
index 2f12dfa..4167592 100644
--- a/pod/perl5110delta.pod
+++ b/pod/perl5110delta.pod
@@ -117,6 +117,20 @@ line match modifier C</s>. (If C<\N> is followed by an opening brace and
 by a letter, perl will still assume that a Unicode character name is
 coming, so compatibility is preserved.) (Rafael Garcia-Suarez)
 
+=head2 Parallel tests
+
+The core distribution can now run its regression tests in parallel on
+Unix-like platforms. Instead of running C<make test>, set C<TEST_JOBS> in
+your environment to the number of tests to run in parallel, and run
+C<make test_harness>. On a Bourne-like shell, this can be done as
+
+    TEST_JOBS=3 make test_harness  # Run 3 tests in parallel
+
+An environment variable is used, rather than parallel make itself, because
+L<TAP::Harness> needs to be able to schedule individual non-conflicting test
+scripts itself, and there is no standard interface to C<make> utilities to
+interact with their job schedulers.
+
 =head1 Modules and Pragmata
 
 =head2 Pragmata Changes