Great...two problems in one. I was not seeing my dies because even though my Build.PL has:
$build->generate_script('t/TEST'); $build->generate_script('t/SMOKE');
The output from perl Build test is:
C:\Development\CPAN\Handel>perl Build test -verbose
C:\Development\Perl\584\bin\perl.exe -I C:\Development\CPAN\Handel\blib\lib -I C:\Development\CPAN\Handel\blib\arch t\SMOKE -clean
So on top of the config issue, it's running t/SMOKE first, and t/TEST is no where in sight....
The same goes for:
#$build->generate_script('t/TEST'); $build->generate_script('t/SMOKE');
-=Chris
So, it looks like SMOKE.PL is triggering my problem.
Question. t/TEST.PL runs TestRunPerl, but t/SMOKE.PL runs TestSmoke, and not TestSmokePerl. Is that right? I'd guess so since smoking worked under EU::MM
For that matter, t/SMOKE shouldn't even be run during test. It should just be t/TEST period. So maybe it's not that SMOKE.PL is causing problems at all, but maybe M::B it trying to run the wrong thing....
Nope... perl t/SMOKE is broken when generated by M::B, but works when generated via EU::MM...
I'm just spouting thoughts hoping it rings someone elses bell... sorry.
-=Chris
smime.p7s
Description: S/MIME Cryptographic Signature