PATH=/usr/bin:/bin:/data/fly2400/cpanfly-5.24/var/megalib/bin
Start 2018-08-26T02:05:17
ActivePerl-2400 CPAN-2.10
Reading '/data/fly2400/cpanfly-5.24/var/cpan/Metadata'
  Database was generated on Sat, 25 Aug 2018 05:54:12 GMT
Checksum for /data/fly2400/cpanfly-5.24/var/cpan/sources/authors/id/F/FE/FELIPE/Crypt-Format-0.09.tar.gz ok
Crypt-Format-0.09/
Crypt-Format-0.09/LICENSE
Crypt-Format-0.09/Changes
Crypt-Format-0.09/MANIFEST
Crypt-Format-0.09/t/
Crypt-Format-0.09/README
Crypt-Format-0.09/META.yml
Crypt-Format-0.09/lib/
Crypt-Format-0.09/Makefile.PL
Crypt-Format-0.09/META.json
Crypt-Format-0.09/lib/Crypt/
Crypt-Format-0.09/lib/Crypt/Format.pm
Crypt-Format-0.09/t/002_convert.t
Crypt-Format-0.09/t/004_custom_base64.t
Crypt-Format-0.09/t/003_normalize.t
Crypt-Format-0.09/t/001_load.t
Configuring F/FE/FELIPE/Crypt-Format-0.09.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 Crypt::Format
Writing MYMETA.yml and MYMETA.json
  FELIPE/Crypt-Format-0.09.tar.gz
  /data/fly2400/ap2400-300558/bin/perl-static Makefile.PL -- OK
Running make for F/FE/FELIPE/Crypt-Format-0.09.tar.gz
>>> make
cp lib/Crypt/Format.pm blib/lib/Crypt/Format.pm
Manifying 1 pod document
  FELIPE/Crypt-Format-0.09.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/001_load.t ........... 
1..1
ok 1 - use Crypt::Format;
ok
t/002_convert.t ........ 
1..6
ok 1 - pem2der() with unix line breaks
ok 2 - … and it doesn’t modify the original string
ok 3 - pem2der() with windows line breaks
ok 4 - PEM conversion looks as expected
ok 5 - … and it round-trips as expected
ok 6 - die() without a WHATSIT
ok
t/003_normalize.t ...... 
1..1
ok 1 - no line longer than 76 chars
ok
t/004_custom_base64.t .. 
1..2
ok 1 - der2pem() (encode())
ok 2 - pem2der() (decode())
ok
All tests successful.
Files=4, Tests=10,  1 wallclock secs ( 0.03 usr  0.02 sys +  0.30 cusr  0.07 csys =  0.42 CPU)
Result: PASS
  FELIPE/Crypt-Format-0.09.tar.gz
  make test TEST_VERBOSE=1 -- OK
<SOFTPKG NAME="Crypt-Format" VERSION="0.09" DATE="2018-08-25">
  <AUTHOR CPAN="FELIPE">Felipe Gasper &lt;felipe@cpan.org></AUTHOR>
  <ABSTRACT>Conversion utilities for encryption applications</ABSTRACT>
  <ARCHITECTURE NAME="x86_64-linux-thread-multi-5.24"/>
  <CODEBASE HREF="Crypt-Format-0.09.tar.gz"/>
  <PROVIDE NAME="Crypt::Format" VERSION="0.09"/>
  <REQUIRE NAME="MIME::Base64" VERSION="0.01"/>
  <!-- Built 2018-08-26 with ActivePerl-2400 on perl-stackato64-precise (Linux perl-stackato64-precise 3.2.0-24-virtual #39-Ubuntu SMP Mon May 21 18:44:18 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux) log Crypt-Format-0.09.d/log-20180826T020517.txt -->
</SOFTPKG>
>>> (cd /data/fly2400/cpanfly-5.24/var/tmp/cpan_build/Crypt-Format-0.09-kFcOfB && tar cvf - Crypt-Format-0.09.ppd blib) | gzip -c >/data/fly2400/cpanfly-5.24/var/REPO/F/FE/FELIPE/Crypt-Format-0.09.tar.gz
Crypt-Format-0.09.ppd
blib/
blib/man3/
blib/man3/Crypt::Format.3
blib/lib/
blib/lib/Crypt/
blib/lib/Crypt/Format.pm
VmSize:	  368192 kB
Finished 2018-08-26T02:05:22