WORKSFORME on Strawberry alpha 2.
I'm betting it's something to do with the -T, because the only
difference I can think of is that the build is running inside some sort
of alternative harness that does something differently...
Out of curiosity, why are your tests set to use tainting?
Adam K
Ovid wrote:
Hi all,
Just discovered there is no ActiveState PPM for Class::BuildMethods on Windows.
The test failure is reported at
http://ppm.activestate.com/BuildStatus/5.8-windows/windows-5.8/Class-BuildMethods-0.111.txt
D:\cpanrun\build\5-8-0\bin\perl.exe "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib\lib', 'blib\arch')" t\00-load.t t\pod-co# Failed test (t\00-load.t at
lidubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 1
Failed 1/1 tests, 0.00% okay
t\pod-coverage....skipped
all skipped: Test::Pod::Coverage 1.04 required for testing POD
coverage
t\pod.............skipped
all skipped: Test::Pod 1.14 required for testing POD
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t\00-load.t 1 256 1 1 100.00% 1
2 tests skipped.
l 5.008, D:\cpanrun\build\5-8-0\bin\perl.exe
# Looks like you failed 1 tests of 1.
Failed 1/3 test scripts, 66.67% okay. 1/1 subtests failed, 0.00% okay.
NMAKE : fatal error U1077: 'D:\cpanrun\build\5-8-0\bin\perl.exe' : return
code '0xff'
Stop.
I have no idea what could possibly be causing this error. The test script
which is failing:
#!perl -T
use Test::More tests => 1;
BEGIN {
use_ok( 'Class::BuildMethods' );
}
diag( "Testing Class::BuildMethods $Class::BuildMethods::VERSION, Perl $],
$^X" );Google has not been helpful, either. Any thoughts?
Cheers,
Ovid
