PATH=/Users/fly2200/bin:/Users/fly2200/ap2200-299195/bin:/Users/fly2200/bin:/Users/fly2200/ap2200-299195/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/Users/fly2200/var/megalib/bin Start 2015-08-12T14:09:49 ActivePerl-2200 CPAN-2.00 Reading '/Users/fly2200/var/cpan/Metadata' Database was generated on Wed, 12 Aug 2015 05:29:02 GMT Running make for R/RJ/RJBS/Process-Status-0.005.tar.gz Fetching with LWP: http://cpan.nas1.activestate.com/authors/id/R/RJ/RJBS/Process-Status-0.005.tar.gz Checksum for /Users/fly2200/var/cpan/sources/authors/id/R/RJ/RJBS/Process-Status-0.005.tar.gz ok Process-Status-0.005 Process-Status-0.005/README Process-Status-0.005/Changes Process-Status-0.005/LICENSE Process-Status-0.005/dist.ini Process-Status-0.005/META.yml Process-Status-0.005/MANIFEST Process-Status-0.005/t Process-Status-0.005/t/basic.t Process-Status-0.005/META.json Process-Status-0.005/Makefile.PL Process-Status-0.005/lib/Process Process-Status-0.005/lib/Process/Status.pm Process-Status-0.005/xt/release Process-Status-0.005/xt/release/pod-syntax.t Process-Status-0.005/t/000-report-versions-tiny.t Process-Status-0.005/xt/release/changes_has_content.t CPAN.pm: Building R/RJ/RJBS/Process-Status-0.005.tar.gz >>> /Users/fly2200/ap2200-299195/bin/perl-dynamic Makefile.PL Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for Process::Status Writing MYMETA.yml and MYMETA.json >>> make cp lib/Process/Status.pm blib/lib/Process/Status.pm Manifying 1 pod document RJBS/Process-Status-0.005.tar.gz make -- OK Running make test >>> make test TEST_VERBOSE=1 PERL_DL_NONLAZY=1 "/Users/fly2200/ap2200-299195/bin/perl-dynamic" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t # # # Generated by Dist::Zilla::Plugin::ReportVersions::Tiny v1.10 # perl: 5.022000 (wanted any version) on darwin from /Users/fly2200/ap2200-299195/bin/perl-dynamic # # ExtUtils::MakeMaker => 7.04 (want 6.30) # Test::More => 1.001014 (want 0.96) # strict => 1.09 (want any version) # warnings => 1.32 (want any version) # # Thanks for using my code. I hope it works for you. # If not, please try and include this output in the bug report. # That will help me reproduce the issue and solve your problem. # t/000-report-versions-tiny.t .. ok 1 - we really didn't test anything, just reporting data 1..1 ok t/basic.t ..................... # Subtest: status_code == 31488 ok 1 - exit status 123 ok 2 - caught no signal ok 3 - did not dump core ok 4 - ->as_struct is as expected ok 5 - ->as_string is as expected 1..5 ok 1 - status_code == 31488 # Subtest: status_code == 395 ok 1 - exit status 1 ok 2 - caught signal 11 ok 3 - dumped core ok 4 - ->as_struct is as expected ok 5 - ->as_string is as expected 1..5 ok 2 - status_code == 395 # Subtest: status_code == -1 ok 1 - exit status 1 ok 2 - didn't catch a signal ok 3 - didn't dump core ok 4 - ->as_struct is as expected ok 5 - ->as_string is as expected 1..5 ok 3 - status_code == -1 1..3 ok All tests successful. Files=2, Tests=4, 0 wallclock secs ( 0.02 usr 0.01 sys + 0.13 cusr 0.02 csys = 0.18 CPU) Result: PASS RJBS/Process-Status-0.005.tar.gz make test TEST_VERBOSE=1 -- OK Ricardo SIGNES <rjbs@cpan.org> a handle on process termination, like $? >>> (cd /Users/fly2200/var/cpan/build/Process-Status-0.005-FOqO6s && tar cvf - Process-Status-0.005.ppd blib) | gzip -c >/Users/fly2200/var/REPO/R/RJ/RJBS/Process-Status-0.005.tar.gz Process-Status-0.005.ppd blib/ blib/lib/ blib/lib/Process/ blib/lib/Process/Status.pm blib/man3/ blib/man3/Process::Status.3 >>> mv /Users/fly2200/var/cpan/build/Process-Status-0.005-FOqO6s/Process-Status-0.005.ppd /Users/fly2200/var/REPO/R/RJ/RJBS Finished 2015-08-12T14:09:52