A user might belong to only a single group

[p5sagit/p5-mst-13.2.git] / t / TEST

diff --git a/t/TEST b/t/TEST
index e34e77e..ef3e478 100755 (executable)
--- a/t/TEST
+++ b/t/TEST
@@ -5,6 +5,10 @@
 
 $| = 1;
 
+# Let tests know they're running in the perl core.  Useful for modules
+# which live dual lives on CPAN.
+$ENV{PERL_CORE} = 1;
+
 # Cheesy version of Getopt::Std.  Maybe we should replace it with that.
 if ($#ARGV >= 0) {
     foreach my $idx (0..$#ARGV) {
@@ -302,34 +306,26 @@ EOT
            warn "Failed $bad test scripts out of $files, $pct% okay.\n";
        }
        warn <<'SHRDLU';
-   ### Since not all tests were successful, you may want to run some
-   ### of them individually and examine any diagnostic messages they
-   ### produce.  See the INSTALL document's section on "make test".
-   ### If you are testing the compiler, then ignore this message
-   ### and run
-   ###      ./perl harness
-   ### in the directory ./t.
+   ### Since not all tests were successful, you may want to run some of
+   ### them individually and examine any diagnostic messages they produce.
+   ### See the INSTALL document's section on "make test".
 SHRDLU
        warn <<'SHRDLU' if $good / $total > 0.8;
-   ###
-   ### Since most tests were successful, you have a good chance to
-   ### get information with better granularity by running
+   ### You have a good chance to get more information by running
    ###     ./perl harness
-   ### in directory ./t.
+   ### in the 't' directory since most (>=80%) of the tests succeeded.
 SHRDLU
        use Config;
        if ($Config{ldlibpthname}) {
            warn <<SHRDLU;
-   ### Since you seem to have a dynamic library search path,
-   ### $Config{ldlibpthname}, you probably should set that
-   ### to point to the build directory before running the harness.
-   ### Depending on your shell style:
-   ###     setenv $Config{ldlibpthname} `pwd`; cd t; ./perl harness
-   ### (for csh-style shells) or:
-   ###     $Config{ldlibpthname}=`pwd`; export $Config{ldlibpthname}; cd t; ./perl harness
-   ### (for traditional Bourne-style shells) or:
-   ###     export $Config{ldlibpthname}=`pwd`; cd t; ./perl harness
-   ### (for ksh-style shells, like zsh).
+   ### You may have to set your dynamic library search path,
+   ### $Config{ldlibpthname}, to point to the build directory
+   ### before running the harness-- depending on your shell style:
+   ###     setenv $Config{ldlibpthname} `pwd`:$Config{ldlibpthname}; cd t; ./perl harness
+   ###     $Config{ldlibpthname}=`pwd`:$Config{ldlibpthname}; export $Config{ldlibpthname}; cd t; ./perl harness
+   ###     export $Config{ldlibpthname}=`pwd`:$Config{ldlibpthname}; cd t; ./perl harness
+   ### for csh-style shells, like tcsh; or for traditional/modern
+   ### Bourne-style shells, like bash, ksh, and zsh, respectively.
 SHRDLU
        }
     }