Re: ENV problems with testing

2005-09-19 Thread Comrade Burnout
James E Keenan wrote:

>  snip 
>
> The thing that puzzled me about Burnout's test failures was that they
> seemed to happen at places where the code was very mundane.  We've
> been communicating on this list, Perlmonks, and off-list about it for
> weeks.  We did confirm that the tests were referencing the old,
> installed version of EU::ModuleMaker, but couldn't figure out why that
> was so.
>
> But if the problem was not, per se, that Burnout was running 5.6.1,
> but that he was running an old version of EU::MakeMaker that kept
> pointing back to the old, installed version of EU::ModuleMaker (keep
> those names straight!), then a lot becomes explicable.  (What follows
> refers to test failure reports Burnout sent me off-list on Sept 7.)
>
> t/02_bad_constructor..Odd number of elements in hash
> assignment at
> /usr/local/lib/perl5/site_perl/5.6.1/ExtUtils/ModuleMaker.pm line 232.
> # Failed test (t/testlib/Auxiliary.pm at line 163)
> #   ''
> # doesn't match '(?-xism:^Must be hash or balanced list of
> key-value pairs:)'
> Odd number of elements in hash assignment at
> /usr/local/lib/perl5/site_perl/5.6.1/ExtUtils/ModuleMaker.pm line 232.
>
> Of course, in the old version of ModuleMaker, the value of AUTHOR was
> a hash of hashes, i.e., a 2-level hash.  In my recent versions, the
> elements in the inner level have been moved up to the top level; the
> value of AUTHOR is a string, not a reference.
>
> t/09_miscargs.Can't locate object method
> "dump_keys" via package "ExtUtils::ModuleMaker" (perhaps you forgot to
> load "ExtUtils::ModuleMaker"?) at t/09_miscargs.t line 178.
> # Looks like you planned 225 tests but only ran 66.
> # Looks like your test died just after 66.
>
> The old, installed version of EU::ModuleMaker had no dump_keys method
> -- so of course it couldn't be found.
>
> Once Burnout upgraded, he got a new version of EU::MakeMaker.  But we
> probably could have fixed the problem *simply* by upgrading MakeMaker.
>
> Burnout:  Do you remember which version of EU::MakeMaker you were using?

well, this may help a bit:

( from /usr/local/lib/perl5/5.6.1/ExtUtils/MakeMaker.pm )

$VERSION = '6.30';
($Revision = q$Revision: 4535 $) =~ /Revision:\s+(\S+)/;

( i can run the tests against the 5.6.1 install still; i just need to
explicitly reference that binary. )

--b--



Re: ENV problems with testing

2005-09-19 Thread Comrade Burnout
Michael G Schwern wrote:

>On Thu, Sep 15, 2005 at 01:32:47PM -0500, Comrade Burnout wrote:
>  
>
>>But, some of the test fail because the previously installed version of
>>EU::MM ends up being used in the tests, and not the version in my local
>>dir (that I'm trying to test)
>>
>>
>
>Do your tests run another copy of Perl?  ie...
>
>system("$^X ...");
>
>If so, it won't have blib/lib and friends in its path.
>  
>
well, that finally answers the question.

i upgraded to 5.8.2 (i think that's the minor version number .. don't
recall), and that "magickally" fixed everything. 

i was running 5.6.1 at the time.


>
>  
>



Re: ENV problems with testing

2005-09-15 Thread Comrade Burnout
James E Keenan wrote:

> [[[ snip ]]]
>
>>>
> [snip]
>
> Let me point out one other anomaly which may not be the source of the
> problem.  In the following line of output 'make' is using the perl
> executable in /usr/bin
>
>>> /usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
>>> blib/script/modulemaker
>>> Manifying blib/man1/modulemaker.1
>>
>
I don't think that matters:

[ burnt ] :: pwd
/usr/bin
[ burnt ] :: ls -al per*
lrwxr-xr-x  1 root  wheel  19 Jul 21  2004 perl -> /usr/local/bin/perl
lrwxr-xr-x  1 root  wheel  19 Jul 21  2004 perl5 -> /usr/local/bin/perl
lrwxr-xr-x  1 root  wheel  19 Jul 21  2004 perl5.6.1 -> /usr/local/bin/perl

and as an added test, i tried:

/usr/local/bin/perl Makefile.PL

on a clean untar ... and the same issues.

I don't get it 

And since it seems to be only the 2 of us, should we take this off-list,
or is it something that's worth keeping on the list for "posterity"

--b--





Re: ENV problems with testing

2005-09-15 Thread Comrade Burnout
James E Keenan wrote:

> And, again, to rule out obvious problems ...
> 1.  When you ran 'make', did you get output that looks more or less
> like this:

FWIW, here's the full output of make ...

> [ burnt ] :: make
> cp lib/ExtUtils/ModuleMaker/StandardText.pm
> blib/lib/ExtUtils/ModuleMaker/StandardText.pm
> cp lib/ExtUtils/ModuleMaker/Utility.pm
> blib/lib/ExtUtils/ModuleMaker/Utility.pm
> cp lib/ExtUtils/ModuleMaker/Interactive.pm
> blib/lib/ExtUtils/ModuleMaker/Interactive.pm
> cp lib/ExtUtils/ModuleMaker/Auxiliary.pm
> blib/lib/ExtUtils/ModuleMaker/Auxiliary.pm
> cp lib/ExtUtils/ModuleMaker/Defaults.pm
> blib/lib/ExtUtils/ModuleMaker/Defaults.pm
> cp lib/ExtUtils/ModuleMaker/Licenses/Standard.pm
> blib/lib/ExtUtils/ModuleMaker/Licenses/Standard.pm
> cp lib/ExtUtils/ModuleMaker/Initializers.pm
> blib/lib/ExtUtils/ModuleMaker/Initializers.pm
> cp lib/ExtUtils/ModuleMaker.pm blib/lib/ExtUtils/ModuleMaker.pm
> cp lib/ExtUtils/ModuleMaker/Licenses/Local.pm
> blib/lib/ExtUtils/ModuleMaker/Licenses/Local.pm
> cp scripts/modulemaker blib/script/modulemaker
> /usr/bin/perl "-MExtUtils::MY" -e "MY->fixin(shift)"
> blib/script/modulemaker
> Manifying blib/man1/modulemaker.1
> Manifying blib/man3/ExtUtils::ModuleMaker::StandardText.3
> Manifying blib/man3/ExtUtils::ModuleMaker::Utility.3
> Manifying blib/man3/ExtUtils::ModuleMaker::Interactive.3
> Manifying blib/man3/ExtUtils::ModuleMaker::Auxiliary.3
> Manifying blib/man3/ExtUtils::ModuleMaker::Defaults.3
> Manifying blib/man3/ExtUtils::ModuleMaker::Licenses::Standard.3
> Manifying blib/man3/ExtUtils::ModuleMaker::Initializers.3
> Manifying blib/man3/ExtUtils::ModuleMaker.3
> Manifying blib/man3/ExtUtils::ModuleMaker::Licenses::Local.3
>
>
> 2.  When you run 'make test', did your output start like this:
>
> [eumm 533]$ make test
> PERL_DL_NONLAZY=1 /usr/local/bin/perl "-MExtUtils::Command::MM" "-e"
> "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
>
[ burnt ] :: make test | more
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/01_ini..ok
Odd number of elements in hash assignment at
/usr/local/lib/perl5/site_perl/5.6.1/ExtUtils/ModuleMaker.pm line 232.
# Failed test
(/opt/source/perl/ExtUtils-ModuleMaker-0.39_10/blib/lib/ExtUtils/ModuleMaker/Auxiliary.pm
at line 224)
#   ''
# doesn't match '(?-xism:^Must be hash or balanced list of key-value
pairs:)'


[ burnt ] :: which perl
/usr/bin/perl


>
> >>(Side issue:  IIRC, the proper way to use the VERBOSE option is:
> >>make test VERBOSE=1
>
> I was wrong in the previous posting.  It should have been:
>
> make test TEST_VERBOSE=1
>
[ burnt ] :: make test TEST_VERBOSE=1 | less
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
t/01_ini..1..11
ok 1 - use ExtUtils::ModuleMaker;
ok 2 - use ExtUtils::ModuleMaker::Utility;
ok 3 - use File::Copy;
ok 4 - use File::Spec;
ok 5 - use Carp;
ok 6 - HOME or home-equivalent directory found on system
ok 7 - personal defaults directory found on system
ok 8 - personal defaults directory temporarily renamed
ok 9 - The object isa ExtUtils::ModuleMaker
ok 10 - personal defaults directory restored
ok 11 - original presence/absence of .modulemaker directory restored
ok
t/02_bad_constructor..1..112
ok 1 - use ExtUtils::ModuleMaker;
ok 2 - use Cwd;
ok 3 - changed to temp directory for testing
ok 4 - personal defaults directory now present on system
ok 5 - personal defaults file not found
ok 6 - personal defaults file not found
Odd number of elements in hash assignment at
/usr/local/lib/perl5/site_perl/5.6.1/ExtUtils/ModuleMaker.pm line 232.
not ok 7 - Constructor correctly failed due to odd number of arguments






Re: ENV problems with testing

2005-09-15 Thread Comrade Burnout
James E Keenan wrote:

> Comrade Burnout wrote:
>
>> I'm not sure this is the right place to ask, but I'm at the end of my
>> rope here.
>>
>>> perl Makefile.pl
>>
> make
>
>>> make test VERBOSE=>1
>>
>>
>>
> Did you include 'make' between 'perl Makefile.PL' and 'make test'?

yes, i did.  i just omitted it in my distracted message earlier ... 

>
> (Side issue:  IIRC, the proper way to use the VERBOSE option is:
> make test VERBOSE=1
> ... but I'm not sure that would make a difference to your main problem.)
>
no, that wouldn't ... it would just affect the make test results .. and
the "special arrow" seemed to work anyway  *shrug*

--brian



ENV problems with testing

2005-09-15 Thread Comrade Burnout
I'm not sure this is the right place to ask, but I'm at the end of my
rope here.

I've been working with the ExtUtils::ModuleMaker author with some
beta-testing of new releases. 

(part of `uname -a`)
FreeBSD 5.2.1-RELEASE

( relevant perl -v )
This is perl, v5.6.1 built for i386-freebsd

I've just run the basics ...

> perl Makefile.pl
> make test VERBOSE=>1

But, some of the test fail because the previously installed version of
EU::MM ends up being used in the tests, and not the version in my local
dir (that I'm trying to test)

Example failure output:

# Looks like your test died just after 63.
Can't use string ("Hilton Stallone") as a HASH ref while "strict refs"
in use at /usr/local/lib/perl5/site_perl/5.6.1/ExtUtils/ModuleMaker.pm
line 470.

Where the version I'm *trying* to test is in:

/opt/source/perl/ExtUtils-ModuleMaker-0.39_10


(I did post to perlmonks.org looking for advice, but adding -Mblib and
running the individual tests yields the same problems.  I've dumped out
@INC, and the first directory (even when passing in blib ) is still
site_perl/5.6.1 and not something form /opt/source  )

I'm completely stuck on what would need fixed on my server.

Thanks in advance,

--brian



Re: Phalanx matchups

2005-02-03 Thread Comrade Burnout

Andy Lester wrote:
I've started a new page on the Kwiki to replace the HereToHelp page:
http://phalanx.kwiki.org/index.cgi?TeamsWanted
Here's where I hope people looking for teams, or teams looking for
people, can get together and join forces.  

I'll put my hat in the ring, first: I don't want to run a module team,
but I'm glad to join one.
 

As long as there's a clear definition of goals and direction ... I don't 
see why I *couldn't* lead a module team, altough my test-fu is ... 
sub-optimal?  still developing?  not quite out of 'wax on, wax off' stages?

I can't say that I'm clear on the Phalanx 100.  I get that it's a nice 
list of modules and all ... but I don't see any assignments or anything 
associated with them -- most likely because there aren't any.

--brian


introduction

2005-01-30 Thread Comrade Burnout
I remember seeing that the list-joining thingie mentioned an 
introduction once someone joined, so here it is:

I'm geektron on perlmonks, and Brian Clarkson IRL.
I've talked a bit to Mr. Lester and Mr. Kinyon about tests, and decided 
that learning some good testing skills while doing something useful 
added up to joining this  list and the Phalanx project.

I'm not sure where to start other than this.  So "hi" and stuff.
Brian