PATH=/usr/bin:/bin:/data/fly2400/cpanfly-5.24/var/megalib/bin Start 2018-04-24T02:16:29 ActivePerl-2400 CPAN-2.10 Reading '/data/fly2400/cpanfly-5.24/var/cpan/Metadata' Database was generated on Mon, 23 Apr 2018 05:17:02 GMT Checksum for /data/fly2400/cpanfly-5.24/var/cpan/sources/authors/id/M/MI/MIYAGAWA/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.tar.gz ok CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/Changes CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/cpanfile CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/dist.ini CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/lib/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/LICENSE CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/Makefile.PL CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/MANIFEST CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/META.json CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/META.yml CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/README CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/t/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/t/author-pod-syntax.t CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/t/basic.t CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/t/Foo.pm CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/t/load.t CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/lib/CPAN/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/lib/CPAN/Test/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/lib/CPAN/Test/Dummy/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/lib/CPAN/Test/Dummy/Perl5/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/lib/CPAN/Test/Dummy/Perl5/UseUnsafeINC/ CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01/lib/CPAN/Test/Dummy/Perl5/UseUnsafeINC/One.pm Configuring M/MI/MIYAGAWA/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.tar.gz with Makefile.PL >>> /data/fly2400/ap2400-300558/bin/perl-static Makefile.PL Checking if your kit is complete... Looks good Have /data/fly2400/cpanfly-5.24/var/megalib Want /home/fly2400/ap2400-300558/lib Your perl and your Config.pm seem to have different ideas about the architecture they are running on. Perl thinks: [megalib] Config says: [x86_64-linux-thread-multi] This may or may not cause problems. Please check your installation of perl if you have problems building this extension. Generating a Unix-style Makefile Writing Makefile for CPAN::Test::Dummy::Perl5::UseUnsafeINC::One Writing MYMETA.yml and MYMETA.json MIYAGAWA/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.tar.gz /data/fly2400/ap2400-300558/bin/perl-static Makefile.PL -- OK Running make for M/MI/MIYAGAWA/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.tar.gz >>> make cp lib/CPAN/Test/Dummy/Perl5/UseUnsafeINC/One.pm blib/lib/CPAN/Test/Dummy/Perl5/UseUnsafeINC/One.pm Manifying 1 pod document MIYAGAWA/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.tar.gz make -- OK Running make test >>> make test TEST_VERBOSE=1 PERL_DL_NONLAZY=1 "/data/fly2400/ap2400-300558/bin/perl-static" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t t/author-pod-syntax.t .. skipped: these tests are for testing by the author t/basic.t .............. ok 1 1..1 ok t/load.t ............... ok 1 1..1 ok All tests successful. Files=3, Tests=2, 0 wallclock secs ( 0.02 usr 0.03 sys + 0.12 cusr 0.06 csys = 0.23 CPU) Result: PASS MIYAGAWA/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.tar.gz make test TEST_VERBOSE=1 -- OK Tatsuhiko Miyagawa <miyagawa@bulknews.net> x_use_unsafe_inc 1 >>> (cd /data/fly2400/cpanfly-5.24/var/tmp/cpan_build/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01-FXSgjF && tar cvf - CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.ppd blib) | gzip -c >/data/fly2400/cpanfly-5.24/var/REPO/M/MI/MIYAGAWA/CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.tar.gz CPAN-Test-Dummy-Perl5-UseUnsafeINC-One-0.01.ppd blib/ blib/man3/ blib/man3/CPAN::Test::Dummy::Perl5::UseUnsafeINC::One.3 blib/lib/ blib/lib/CPAN/ blib/lib/CPAN/Test/ blib/lib/CPAN/Test/Dummy/ blib/lib/CPAN/Test/Dummy/Perl5/ blib/lib/CPAN/Test/Dummy/Perl5/UseUnsafeINC/ blib/lib/CPAN/Test/Dummy/Perl5/UseUnsafeINC/One.pm VmSize: 363316 kB Finished 2018-04-24T02:16:34