William McKee wrote:
I'm just spouting thoughts hoping it rings someone elses bell... sorry.


This reminds me of a discussion that took place recently on the MB
mailing list[1]. I wonder what would happen if you leave SMOKE.PL but
comment out all the code. Do the die statements get called? Perhaps
something in that code is short-circuting A::T.


William

[1] 
http://sourceforge.net/mailarchive/forum.php?thread_id=6951616&forum_id=10905

I think I've found the culprit.

If I do:

perl Makefile.PL
        (which calls generate_script for TEST.PL and then SMOKE.PL)
perl t/TEST
perl t/SMOKE

Everything runs as expected. However if I do:

perl Makefile.PL
perl t/SMOKE

it starts the endless "where's apache" loop. I'm assuming that is because t/conf/apache_test_config.pm has not yet been generated by running t/TEST || TestRunPerl.

Is that expected, or is that a bug?


Now this problem cropped up because M::B, or TestMB is inadvertantly trying to run SMOKE instead of TEST during 'perl Build test'.

Even more fascinating....

If I switch:

$build->generate_script('t/TEST');
$build->generate_script('t/SMOKE');

to this:

$build->generate_script('t/SMOKE');
$build->generate_script('t/TEST');

perl Build test runs just fine...and perl t/SMOKE then runs fine as well. And just for a laugh....

$build->generate_script('t/SMOKE');
$build->generate_script('t/TEST');
$build->generate_script('t/POOP');

yields:

C:\Development\CPAN\Handel>perl Build test
C:\Development\Perl\584\bin\perl.exe -I C:\Development\CPAN\Handel\blib\lib -I 
C:\Development\CPAN\Handel\blib\arch t\POOP -clean



So, apparently it's trying to run the last script created via generate_script instead of always running t/TEST.

-=Chris

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to