PATH=/usr/bin:/bin:/data/fly2400/cpanfly-5.24/var/megalib/bin
Start 2018-10-28T02:00:38
ActivePerl-2400 CPAN-2.10
Reading '/data/fly2400/cpanfly-5.24/var/cpan/Metadata'
  Database was generated on Sat, 27 Oct 2018 05:41:02 GMT
Checksum for /data/fly2400/cpanfly-5.24/var/cpan/sources/authors/id/F/FE/FELIPE/Call-Context-0.03.tar.gz ok
Call-Context-0.03/
Call-Context-0.03/LICENSE
Call-Context-0.03/Changes
Call-Context-0.03/MANIFEST
Call-Context-0.03/t/
Call-Context-0.03/Todo
Call-Context-0.03/README.pod
Call-Context-0.03/.gitignore
Call-Context-0.03/META.yml
Call-Context-0.03/lib/
Call-Context-0.03/Makefile.PL
Call-Context-0.03/.travis.yml
Call-Context-0.03/META.json
Call-Context-0.03/lib/Call/
Call-Context-0.03/lib/Call/Context.pm
Call-Context-0.03/t/003_must_not_be_scalar.t
Call-Context-0.03/t/002_must_be_list.t
Call-Context-0.03/t/001_load.t
Configuring F/FE/FELIPE/Call-Context-0.03.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 Call::Context
Writing MYMETA.yml and MYMETA.json
  FELIPE/Call-Context-0.03.tar.gz
  /data/fly2400/ap2400-300558/bin/perl-static Makefile.PL -- OK
Running make for F/FE/FELIPE/Call-Context-0.03.tar.gz
>>> make
cp lib/Call/Context.pm blib/lib/Call/Context.pm
cp README.pod blib/lib/Call/README.pod
Manifying 1 pod document
  FELIPE/Call-Context-0.03.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 Call::Context;
ok
t/002_must_be_list.t ........ 
1..6
ok 1 - An object of class 'Call::Context::X' isa 'Call::Context::X'
ok 2 - called function is in message
ok 3 - calling function is in message
ok 4 - context is in message (void)
ok 5 - context is in message (scalar)
ok 6 - no die() if in list context
ok
t/003_must_not_be_scalar.t .. 
1..6
ok 1 - An object of class 'Call::Context::X' isa 'Call::Context::X'
ok 2 - called function is in message
ok 3 - calling function is in message
ok 4 - context is in message
ok 5 - no die() if in void context
ok 6 - no die() if in list context
ok
All tests successful.
Files=3, Tests=13,  1 wallclock secs ( 0.04 usr  0.01 sys +  0.23 cusr  0.05 csys =  0.33 CPU)
Result: PASS
  FELIPE/Call-Context-0.03.tar.gz
  make test TEST_VERBOSE=1 -- OK
<SOFTPKG NAME="Call-Context" VERSION="0.03" DATE="2018-10-27">
  <AUTHOR CPAN="FELIPE">Felipe Gasper &lt;felipe@cpan.org></AUTHOR>
  <ABSTRACT>Sanity-check calling context</ABSTRACT>
  <ARCHITECTURE NAME="x86_64-linux-thread-multi-5.24"/>
  <CODEBASE HREF="Call-Context-0.03.tar.gz"/>
  <PROVIDE NAME="Call::Context" VERSION="0.03"/>
  <!-- Built 2018-10-28 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 Call-Context-0.03.d/log-20181028T020038.txt -->
</SOFTPKG>
>>> (cd /data/fly2400/cpanfly-5.24/var/tmp/cpan_build/Call-Context-0.03-dD9UtB && tar cvf - Call-Context-0.03.ppd blib) | gzip -c >/data/fly2400/cpanfly-5.24/var/REPO/F/FE/FELIPE/Call-Context-0.03.tar.gz
Call-Context-0.03.ppd
blib/
blib/man3/
blib/man3/Call::Context.3
blib/lib/
blib/lib/Call/
blib/lib/Call/README.pod
blib/lib/Call/Context.pm
VmSize:	  370332 kB
Finished 2018-10-28T02:00:43