From: Jesse Vincent <jesse@bestpractical.com>
Date: Wed, 30 Sep 2009 17:54:27 +0000 (+0900)
Subject: describe parallel testing in perlhack.pod
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=a75f557cc482d1753211634e8aac8b7572677015;p=p5sagit%2Fp5-mst-13.2.git

describe parallel testing in perlhack.pod
---

diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index be860ee..736dd6c 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -1959,6 +1959,23 @@ you can say
     nmake test TEST_FILES="op/*.t"
     nmake test TEST_SWITCHES="-torture" TEST_FILES="op/*.t"
 
+=item 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.
+
+Note that currently some test scripts may fail when run in parallel (most
+notably C<ext/IO/t/io_dir.t>). If necessary run just the failing scripts
+again sequentially and see if the failures go away.
 =item test-notty test_notty
 
 Sets PERL_SKIP_TTY_TEST to true before running normal test.