Click here to get back home

Test::Harness overloading of PERL5LIB
 Home | NewsGroups | Search | About
Login Password
Register Now!
 comp.lang.perl.modules    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
Test::Harness overloading of PERL5LIB Daniel E. Macks 02-07-2006
Posted by Daniel E. Macks on February 7, 2006, 3:46 pm
Please log in for more thread options

It appears Test::Harness stores its @INC in $ENV when
running the test scripts:

% echo $PERL5LIB
/sw/lib/perl5:/sw/lib/perl5/darwin

% perl5.8.1 -e 'print "@INC\n"'
/sw/lib/perl5/5.8.1/darwin-thread-multi-2level /sw/lib/perl5/5.8.1
/sw/lib/perl5/darwin-thread-multi-2level /sw/lib/perl5 /sw/lib/perl5/darwin
/System/Library/Perl/5.8.1/darwin-thread-multi-2level /System/Library/Perl/5.8.1
/Library/Perl/5.8.1/darwin-thread-multi-2level /Library/Perl/5.8.1 /Library/Perl
/Network/Library/Perl/5.8.1/darwin-thread-multi-2level
/Network/Library/Perl/5.8.1 /Network/Library/Perl .

% cat foo.t
use Test::More no_plan;
warn "\n";
warn "$ENV\n";

% perl5.8.1 -MTest::Harness -e 'runtests("foo.t")'
foo...

./sw/lib/perl5/5.8.1/darwin-thread-multi-2level:/sw/lib/perl5/5.8.1:/sw/lib/perl5/darwin-thread-multi-2level:/sw/lib/perl5:/sw/lib/perl5/darwin:/System/Library/Perl/5.8.1/darwin-thread-multi-2level:/System/Library/Perl/5.8.1:/Library/Perl/5.8.1/darwin-thread-multi-2level:/Library/Perl/5.8.1:/Library/Perl:/Network/Library/Perl/5.8.1/darwin-thread-multi-2level:/Network/Library/Perl/5.8.1:/Network/Library/Perl:.

If the test script (or anywhere in whatever it's testing) does a
system(perl), that inner perl has the parent perl interpretter's @INC
ahead of its own. That ranges between an unrealistic test environment
and a fatal error:

% cat bar.t
use Test::More no_plan;
warn "\n";
system q{perl5.8.6 -e 'warn "@INC\n"'};
system "perl5.8.6 -MConfig -e 'exit'";

% perl5.8.1 -MTest::Harness -e 'runtests("bar.t")'
bar...
./sw/lib/perl5/5.8.1/darwin-thread-multi-2level
/sw/lib/perl5/5.8.1/darwin-thread-multi-2level /sw/lib/perl5/5.8.1
/sw/lib/perl5/darwin-thread-multi-2level
/sw/lib/perl5/5.8.6/darwin-thread-multi-2level /sw/lib/perl5/5.8.6
/sw/lib/perl5/darwin-thread-multi-2level
/sw/lib/perl5/5.8.6/darwin-thread-multi-2level /sw/lib/perl5/5.8.1 /sw/lib/perl5
/sw/lib/perl5/darwin /System/Library/Perl/5.8.1/darwin-thread-multi-2level
/System/Library/Perl/5.8.1/darwin-thread-multi-2level /System/Library/Perl/5.8.1
/Library/Perl/5.8.1/darwin-thread-multi-2level
/Library/Perl/5.8.1/darwin-thread-multi-2level /Library/Perl/5.8.1
/Library/Perl/5.8.1 /Library/Perl
/Network/Library/Perl/5.8.1/darwin-thread-multi-2level
/Network/Library/Perl/5.8.1 /Network/Library/Perl .
/sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level /sw/lib/perl5-core/5.8.6
/sw/lib/perl5/site_perl/5.8.6/darwin-thread-multi-2level
/sw/lib/perl5/site_perl/5.8.6
/sw/lib/perl5/site_perl/5.8.6/darwin-thread-multi-2level /sw/lib/perl5/site_perl
.
Perl lib version (5.8.1) doesn't match executable version (5.8.6) at
/System/Library/Perl/5.8.1/darwin-thread-multi-2level/Config.pm line 33.
Compilation failed in require.
BEGIN failed--compilation aborted.

I see the same effect with Test::Harness as supplied with perl5.8.1 or
perl5.8.6 (i.e., can swap the outer and inner perl versions).

dan

--
Daniel Macks
dmacks@netspace.org
http://www.netspace.org/~dmacks


Posted by harryfmudd [AT] comcast [DOT] on February 7, 2006, 10:40 pm
Please log in for more thread options

Daniel E. Macks wrote:
> It appears Test::Harness stores its @INC in $ENV when
> running the test scripts:
>
> % echo $PERL5LIB
> /sw/lib/perl5:/sw/lib/perl5/darwin
>
> % perl5.8.1 -e 'print "@INC\n"'
> /sw/lib/perl5/5.8.1/darwin-thread-multi-2level /sw/lib/perl5/5.8.1
/sw/lib/perl5/darwin-thread-multi-2level /sw/lib/perl5 /sw/lib/perl5/darwin
/System/Library/Perl/5.8.1/darwin-thread-multi-2level /System/Library/Perl/5.8.1
/Library/Perl/5.8.1/darwin-thread-multi-2level /Library/Perl/5.8.1 /Library/Perl
/Network/Library/Perl/5.8.1/darwin-thread-multi-2level
/Network/Library/Perl/5.8.1 /Network/Library/Perl .
>
> % cat foo.t
> use Test::More no_plan;
> warn "\n";
> warn "$ENV\n";
>
> % perl5.8.1 -MTest::Harness -e 'runtests("foo.t")'
> foo...
>
./sw/lib/perl5/5.8.1/darwin-thread-multi-2level:/sw/lib/perl5/5.8.1:/sw/lib/perl5/darwin-thread-multi-2level:/sw/lib/perl5:/sw/lib/perl5/darwin:/System/Library/Perl/5.8.1/darwin-thread-multi-2level:/System/Library/Perl/5.8.1:/Library/Perl/5.8.1/darwin-thread-multi-2level:/Library/Perl/5.8.1:/Library/Perl:/Network/Library/Perl/5.8.1/darwin-thread-multi-2level:/Network/Library/Perl/5.8.1:/Network/Library/Perl:.
>
> If the test script (or anywhere in whatever it's testing) does a
> system(perl), that inner perl has the parent perl interpretter's @INC
> ahead of its own. That ranges between an unrealistic test environment
> and a fatal error:
>
> % cat bar.t
> use Test::More no_plan;
> warn "\n";
> system q{perl5.8.6 -e 'warn "@INC\n"'};
> system "perl5.8.6 -MConfig -e 'exit'";
>
> % perl5.8.1 -MTest::Harness -e 'runtests("bar.t")'
> bar...
> ./sw/lib/perl5/5.8.1/darwin-thread-multi-2level
/sw/lib/perl5/5.8.1/darwin-thread-multi-2level /sw/lib/perl5/5.8.1
/sw/lib/perl5/darwin-thread-multi-2level
/sw/lib/perl5/5.8.6/darwin-thread-multi-2level /sw/lib/perl5/5.8.6
/sw/lib/perl5/darwin-thread-multi-2level
/sw/lib/perl5/5.8.6/darwin-thread-multi-2level /sw/lib/perl5/5.8.1 /sw/lib/perl5
/sw/lib/perl5/darwin /System/Library/Perl/5.8.1/darwin-thread-multi-2level
/System/Library/Perl/5.8.1/darwin-thread-multi-2level /System/Library/Perl/5.8.1
/Library/Perl/5.8.1/darwin-thread-multi-2level
/Library/Perl/5.8.1/darwin-thread-multi-2level /Library/Perl/5.8.1
/Library/Perl/5.8.1 /Library/Perl
/Network/Library/Perl/5.8.1/darwin-thread-multi-2level
/Network/Library/Perl/5.8.1 /Network/Library/Perl .
/sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level /sw/lib/perl5-core/5.8.6
/sw/lib/perl5/site_perl/5.8.6/darwin-thread-multi-2level
/sw/lib/perl5/site_perl/5.8.6
/sw/lib/perl5/site_perl/5.8.6/darwin-thread-multi-2level /sw/lib/p
erl5/site_perl .
> Perl lib version (5.8.1) doesn't match executable version (5.8.6) at
/System/Library/Perl/5.8.1/darwin-thread-multi-2level/Config.pm line 33.
> Compilation failed in require.
> BEGIN failed--compilation aborted.
>
> I see the same effect with Test::Harness as supplied with perl5.8.1 or
> perl5.8.6 (i.e., can swap the outer and inner perl versions).
>
> dan
>

Yes, it does appear that that is what's happening. And I believe it
wouldn't make any difference if there weren't two (or three!) different
versions of Perl involved - two from Fink and (maybe!) one that came
with Panther (if that's what the /System/Library stuff represents). It
seems reasonable to me that this is a situation the authors of
Test::Harness didn't anticipate.

The thing that comes readily to mind is to write a shell script that
resets PERL5LIB to where you want it and then runs Perl. Read the man
page for your favorite shell about passing parameters in. Then have your
top-level Perl run the shell script.

If this isn't helpful, please supply more information. I assumed Fink
based on the /sw/lib..., and Fink implies Mac OS (which /System/Library
seems to confirm), but /System/Library/Perl/5.8.1 implies Mac OS 10.3
(i.e. Panther). But I could be way out of line.

Just for my curiosity - why in the _WORLD_ would you want to do such a
thing? It makes my head hurt just thinking about it.

Tom Wyant

Posted by Daniel E. Macks on February 15, 2006, 1:31 am
Please log in for more thread options


harryfmudd [AT] comcast [DOT] net <> said:
> Daniel E. Macks wrote:
>> It appears Test::Harness stores its @INC in $ENV when
>> running the test scripts:
[snip evidence]
> Yes, it does appear that that is what's happening. And I believe it
> wouldn't make any difference if there weren't two (or three!) different
> versions of Perl involved - two from Fink and (maybe!) one that came
> with Panther (if that's what the /System/Library stuff represents). It
> seems reasonable to me that this is a situation the authors of
> Test::Harness didn't anticipate.
>
> The thing that comes readily to mind is to write a shell script that
> resets PERL5LIB to where you want it and then runs Perl. Read the man
> page for your favorite shell about passing parameters in. Then have your
> top-level Perl run the shell script.

I don't know a reliable and general way to pass that wrapper script
into an arbitrary user of Test::Harness unless it were to replace the
perl interpretter file itself (/usr/bin/perl5.8.1 a wrapper around
/usr/bin/perl5.8.1-real). That's too fundamental a change to make IMO,
and requires perpetually remembering about it when upgrading perl.
It's also a non-trivial wrapper to write because it has to reimplement
the whole @INC determination algorithm, which uses lots of data that
is only really known by that perl interp itself. Either it's a
catch-22 (determined on-the-fly) or very fragile (hard-coded when
wrapper is created, breaks when perl is upgraded or rebuilt with
different options).

OTOH, that was the solution we used for the specific case at hand...

> If this isn't helpful, please supply more information. I assumed Fink
> based on the /sw/lib..., and Fink implies Mac OS (which /System/Library
> seems to confirm), but /System/Library/Perl/5.8.1 implies Mac OS 10.3
> (i.e. Panther). But I could be way out of line.

Correct assumptions about my perl suppliers. The reverse case was done
on OS X 10.4, where Apple supplies perl5.8.6 and fink supplies 5.8.1.

> Just for my curiosity - why in the _WORLD_ would you want to do such a
> thing? It makes my head hurt just thinking about it.

Much of fink itself is written in perl, including the functions
involved in actually building packages. Packages of perl modules are
specific to a certain perl version--fink has multiple perl versions
available to complement the one Apple supplies. Fink's own test suite
tests that the package builder can figure out details about the
various specific perl versions. That means get_perl.t runs as
perl5.8.x and it runs system("perl5.8.y -V").

Since reading Config.pm is really all fink's get_perl() needs to do,
it can just nuke PERL5LIB entirely:
system("/usr/bin/env -i perl5.8.y -V")
instead of trying to reset it to "what perl5.8.y would normally see if
its parent hadn't messed with it".

dan

--
Daniel Macks
dmacks@netspace.org
http://www.netspace.org/~dmacks


Posted by Daniel E. Macks on March 3, 2006, 12:28 am
Please log in for more thread options


harryfmudd [AT] comcast [DOT] net <> said:
> Daniel E. Macks wrote:
>> It appears Test::Harness stores its @INC in $ENV when
>> running the test scripts:
[proof]
>> I see the same effect with Test::Harness as supplied with perl5.8.1 or
>> perl5.8.6 (i.e., can swap the outer and inner perl versions).
>
> Yes, it does appear that that is what's happening. And I believe it
> wouldn't make any difference if there weren't two (or three!) different
> versions of Perl involved - two from Fink and (maybe!) one that came
> with Panther (if that's what the /System/Library stuff represents). It
> seems reasonable to me that this is a situation the authors of
> Test::Harness didn't anticipate.

It appears this has been fixed in newer versions Test::Harness.
Version 2.56, the latest stable on CPAN, works, and from its Changes
file:

2.43_02 Thu Nov 25 00:20:36 CST 2004
[FIXES]
* Test::Harness now removes default paths from the paths that it
sets in PERL5LIB. This fixes RT #5649. Thanks, Schwern.

So it's fixed in perl core too, starting in 5.8.7, i.e., just after
the perl versions I had tested:(

dan

--
Daniel Macks
dmacks@netspace.org
http://www.netspace.org/~dmacks


Posted by harryfmudd [AT] comcast [DOT] on March 3, 2006, 10:52 am
Please log in for more thread options


Daniel E. Macks wrote:
> harryfmudd [AT] comcast [DOT] net <> said:
>
>>Daniel E. Macks wrote:
>>
>>>It appears Test::Harness stores its @INC in $ENV when
>>>running the test scripts:
>
> [proof]
>
>>>I see the same effect with Test::Harness as supplied with perl5.8.1 or
>>>perl5.8.6 (i.e., can swap the outer and inner perl versions).
>>
>>Yes, it does appear that that is what's happening. And I believe it
>>wouldn't make any difference if there weren't two (or three!) different
>>versions of Perl involved - two from Fink and (maybe!) one that came
>>with Panther (if that's what the /System/Library stuff represents). It
>>seems reasonable to me that this is a situation the authors of
>>Test::Harness didn't anticipate.
>
>
> It appears this has been fixed in newer versions Test::Harness.
> Version 2.56, the latest stable on CPAN, works, and from its Changes
> file:
>
> 2.43_02 Thu Nov 25 00:20:36 CST 2004
> [FIXES]
> * Test::Harness now removes default paths from the paths that it
> sets in PERL5LIB. This fixes RT #5649. Thanks, Schwern.
>
> So it's fixed in perl core too, starting in 5.8.7, i.e., just after
> the perl versions I had tested:(
>
> dan
>

Wonderful. Does that mean we'll be seeing a Perl 5.8.8 in Fink?

Tom Wyant

Similar ThreadsPosted
Side effects of overloading quotes "" November 28, 2007, 3:07 pm
Test::Pod problems March 3, 2007, 1:04 am
test fails May 10, 2008, 1:17 pm
Asking questions in 'make test' July 27, 2004, 12:55 am
'make test' strangeness ? August 18, 2004, 4:10 am
Start server for test ? May 16, 2005, 12:52 pm
GD make test problem November 23, 2004, 6:32 am
[ANNOUNCE] Test::MockRandom 0.92 December 23, 2004, 7:49 am
GD make test failure January 16, 2005, 5:11 pm
ANNOUNCE: Test::MockDBI v0.50 January 19, 2005, 9:10 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap