PATH=C:\cpanfly-5.24-64\var\megalib\bin;C:\Perl-5.24-64\site\bin;C:\Perl-5.24-64\bin;C:\MinGW-64\bin;C:\cygwin\bin;C:\instantclient_11_2-64;C:\cpanfly-5.24-64\var\megalib\bin;C:\Perl-5.24-64\site\bin;C:\Perl-5.24-64\bin;C:\MinGW-64\bin;C:\cygwin\bin;C:\instantclient_11_2-64;C:\cpanfly-5.24-64\var\megalib\bin;C:\Perl-5.24-64\site\bin;C:\Perl-5.24-64\bin;C:\MinGW-64\bin;C:\cygwin\bin;C:\instantclient_11_2-64;C:\p4;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files (x86)\CMake\bin Start 2016-10-23T15:14:12 ActivePerl-2400 CPAN-2.10 PATH=C:/CPANFL~1.24-/var/libs/bin;C:\CPANFL~1.24-\var\megalib\bin;C:\PERL-5~1.24-\site\bin;C:\PERL-5~1.24-\bin;C:\MinGW-64\bin;C:\cygwin\bin;C:\INSTAN~1;C:\CPANFL~1.24-\var\megalib\bin;C:\PERL-5~1.24-\site\bin;C:\PERL-5~1.24-\bin;C:\MinGW-64\bin;C:\cygwin\bin;C:\INSTAN~1;C:\CPANFL~1.24-\var\megalib\bin;C:\PERL-5~1.24-\site\bin;C:\PERL-5~1.24-\bin;C:\MinGW-64\bin;C:\cygwin\bin;C:\INSTAN~1;C:\p4;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WINDOW~1\v1.0\;C:\PROGRA~1\Git\cmd;C:\PROGRA~2\CMake\bin Reading 'C:\cpanfly-5.24-64\var\cpan\Metadata' Database was generated on Sun, 23 Oct 2016 06:17:02 GMT Checksum for C:\cpanfly-5.24-64\var\cpan\sources\authors\id\C\CH\CHROMATIC\B-XPath-0.01.tar.gz ok B-XPath-0.01/ B-XPath-0.01/META.yml B-XPath-0.01/Changes B-XPath-0.01/t/ B-XPath-0.01/t/pod-coverage.t B-XPath-0.01/t/find_global_name.t B-XPath-0.01/t/00-load.t B-XPath-0.01/t/pod.t B-XPath-0.01/t/base.t B-XPath-0.01/lib/ B-XPath-0.01/lib/B/ B-XPath-0.01/lib/B/XPath.pm B-XPath-0.01/MANIFEST B-XPath-0.01/Makefile.PL B-XPath-0.01/Build.PL B-XPath-0.01/README B-XPath-0.01/SIGNATURE Configuring C/CH/CHROMATIC/B-XPath-0.01.tar.gz with Makefile.PL >>> C:\Perl-5.24-64\bin\perl.exe Makefile.PL Checking if your kit is complete... Looks good Have \cpanfl~1.24-\var\megalib Want \perl-5~1.24-\lib Your perl and your Config.pm seem to have different ideas about the architecture they are running on. Perl thinks: [megalib] Config says: [MSWin32-x64-multi-thread] This may or may not cause problems. Please check your installation of perl if you have problems building this extension. Generating a dmake-style Makefile Writing Makefile for B::XPath Writing MYMETA.yml and MYMETA.json CHROMATIC/B-XPath-0.01.tar.gz C:\Perl-5.24-64\bin\perl.exe Makefile.PL -- OK Running make for C/CH/CHROMATIC/B-XPath-0.01.tar.gz >>> dmake cp lib/B/XPath.pm blib\lib\B\XPath.pm CHROMATIC/B-XPath-0.01.tar.gz dmake -- OK Running make test >>> dmake test TEST_VERBOSE=1 "C:\Perl-5.24-64\bin\perl.exe" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib\lib', 'blib\arch')" t/*.t # Testing B::XPath 0.01, Perl 5.024000, C:\Perl-5.24-64\bin\perl.exe t/00-load.t ........... 1..1 ok 1 - use B::XPath; ok # Failed test 'shift should have one child' # at t/base.t line 44. # got: '0' # expected: '1' Can't call method "get_name" on an undefined value at t/base.t line 45. # Looks like your test exited with 255 just after 15. t/base.t .............. 1..31 ok 1 - use B::XPath; ok 2 - An object of class 'B::XPath::UNOP' isa 'B::XPath::UNOP' ok 3 - ... with one child ok 4 - ... a lineseq op ok 5 - lineseq should have four children ok 6 - ... a COP ok 7 - ... a scalar assignment ok 8 - ... another COP ok 9 - ... and a return ok 10 - get_nextstate() for assignment should find closest previous COP ok 11 - get_nextstate() for return should find closest previous COP ok 12 - sassign should have two children ok 13 - ... one a shift ok 14 - ... and the other a scalar pad op not ok 15 - shift should have one child Dubious, test returned 255 (wstat 65280, 0xff00) Failed 17/31 subtests Use of uninitialized value $value in string eq at C:/cpanfly-5.24-64/var/megalib/Class/XPath.pm line 211. Use of uninitialized value $value in string eq at C:/cpanfly-5.24-64/var/megalib/Class/XPath.pm line 211. Use of uninitialized value $value in string eq at C:/cpanfly-5.24-64/var/megalib/Class/XPath.pm line 211. Unimplemented method NAME for B::XPath::PADOP=HASH(0x2d4e448) # Looks like your test exited with 255 just after 1. t/find_global_name.t .. 1..16 ok 1 - use B::XPath; Dubious, test returned 255 (wstat 65280, 0xff00) Failed 15/16 subtests t/pod-coverage.t ...... 1..1 ok 1 - Pod coverage on B::XPath ok t/pod.t ............... 1..1 ok 1 - POD test for blib/lib/B/XPath.pm ok Test Summary Report ------------------- t/base.t (Wstat: 65280 Tests: 15 Failed: 1) Failed test: 15 Non-zero exit status: 255 Parse errors: Bad plan. You planned 31 tests but ran 15. t/find_global_name.t (Wstat: 65280 Tests: 1 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 16 tests but ran 1. Files=5, Tests=19, 2 wallclock secs ( 0.05 usr + 0.02 sys = 0.06 CPU) Result: FAIL Failed 2/5 test programs. 1/19 subtests failed. dmake: Error code 255, while making 'test_dynamic' CHROMATIC/B-XPath-0.01.tar.gz dmake test TEST_VERBOSE=1 -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports CHROMATIC/B-XPath-0.01.tar.gz Finished 2016-10-23T15:14:26