simcop2387/cpantestlogs
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
cpantestlogs/NCBIx::eUtils::GeneAliases_genfailure.log
ryan 4fe8bf59aa Second run of tests
2017-05-02 18:44:36 -07:00

179 lines
14 KiB
Text
Raw Permalink Blame History

perl-blead
==========
cpanm (App::cpanminus) 1.7043 on perl 5.026000 built for x86_64-linux
Work directory is /home/ryan/.cpanm/work/1493618087.27736
You have make /usr/bin/make
You have LWP 6.26
You have /bin/tar: tar (GNU tar) 1.29
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
You have /usr/bin/unzip
Searching NCBIx::eUtils::GeneAliases () on cpanmetadb ...
Unpacking NCBIx-eUtils-GeneAliases-0.90.tar.gz
--> Working on NCBIx::eUtils::GeneAliases
Fetching http://www.cpan.org/authors/id/R/RO/ROGERHALL/NCBIx-eUtils-GeneAliases-0.90.tar.gz ... OK
NCBIx-eUtils-GeneAliases/Changes
NCBIx-eUtils-GeneAliases/lib/
NCBIx-eUtils-GeneAliases/lib/NCBIx/
NCBIx-eUtils-GeneAliases/lib/NCBIx/eUtils/
NCBIx-eUtils-GeneAliases/lib/NCBIx/eUtils/GeneAliases.pm
NCBIx-eUtils-GeneAliases/Makefile.PL
NCBIx-eUtils-GeneAliases/MANIFEST
NCBIx-eUtils-GeneAliases/README
NCBIx-eUtils-GeneAliases/scripts/
NCBIx-eUtils-GeneAliases/scripts/get_aliases.pp
NCBIx-eUtils-GeneAliases/scripts/eutils_example.pl
NCBIx-eUtils-GeneAliases/t/
NCBIx-eUtils-GeneAliases/t/pod-coverage.t
NCBIx-eUtils-GeneAliases/t/perlcritic.t
NCBIx-eUtils-GeneAliases/t/pod.t
NCBIx-eUtils-GeneAliases/t/00.load.t
Entering NCBIx-eUtils-GeneAliases
META.yml/json not found. Creating skeleton for it.
Running Makefile.PL
Configuring NCBIx-eUtils-GeneAliases-0.90 ... Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for NCBIx::eUtils::GeneAliases
Writing MYMETA.yml and MYMETA.json
Checking dependencies from MYMETA.json ...
Checking if you have Test::More 0 ... Yes (1.302083)
Checking if you have ExtUtils::MakeMaker 0 ... Yes (7.24)
Checking if you have version 0 ... Yes (0.9918)
OK
Building and testing NCBIx-eUtils-GeneAliases-0.9.0 ... cp lib/NCBIx/eUtils/GeneAliases.pm blib/lib/NCBIx/eUtils/GeneAliases.pm
Manifying 1 pod document
PERL_DL_NONLAZY=1 "/home/ryan/perl5/perlbrew/perls/perl-blead/bin/perl5.26.0" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
# Testing NCBIx::eUtils::GeneAliases 0.9.0
t/00.load.t ....... ok
# Failed test 'Test::Perl::Critic for "blib/lib/NCBIx/eUtils/GeneAliases.pm"'
# at /home/ryan/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.26.0/Test/Perl/Critic.pm line 104.
#
# Variable, subroutine, and package names have to be in CamelCase at line 12, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 13, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 14, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 17, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 18, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 21, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 21, column 28. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 21, column 36. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 22, column 3. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 22, column 25. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 26, column 2. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 27, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 27, column 15. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 28, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 29, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 32, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 32, column 19. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 32, column 40. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 34, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 36, column 4. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 39, column 15. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 39, column 26. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 39, column 40. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 40, column 7. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 40, column 33. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 43, column 15. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 43, column 27. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 44, column 10. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 45, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 45, column 22. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 46, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 46, column 34. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 47, column 17. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 47, column 27. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 47, column 45. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 47, column 56. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 47, column 67. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 47, column 80. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 47, column 80. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 47, column 94. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 49, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 50, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 50, column 22. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 51, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 51, column 34. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 52, column 17. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 52, column 26. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 52, column 45. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 52, column 56. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 52, column 56. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 52, column 70. (no explanation). (Severity: 5)
# "return" statement followed by "sort" at line 56, column 4. Behavior is undefined if called in scalar context. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 56, column 22. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 63, column 2. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 64, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 64, column 15. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 65, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 66, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 66, column 28. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 67, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 67, column 28. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 68, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 71, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 71, column 17. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 73, column 6. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 73, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 77, column 3. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 84, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 84, column 27. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 84, column 47. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 84, column 60. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 85, column 7. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 85, column 17. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 90, column 4. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 90, column 22. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 96, column 10. (no explanation). (Severity: 5)
t/perlcritic.t ....
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
# Failed test 'Pod coverage on NCBIx::eUtils::GeneAliases'
# at /home/ryan/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.26.0/Test/Pod/Coverage.pm line 133.
# Coverage for NCBIx::eUtils::GeneAliases is 0.0%, with 2 naked subroutines:
# START
# get_aliases
# Looks like you failed 1 test of 1.
t/pod-coverage.t ..
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
t/pod.t ........... ok
Test Summary Report
-------------------
t/perlcritic.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
t/pod-coverage.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Files=4, Tests=4, 0 wallclock secs ( 0.01 usr 0.00 sys + 0.70 cusr 0.04 csys = 0.75 CPU)
Result: FAIL
Failed 2/4 test programs. 2/4 subtests failed.
Makefile:845: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
! Installing NCBIx::eUtils::GeneAliases failed. See /home/ryan/.cpanm/work/1493618087.27736/build.log for details. Retry with --force to force install it.
FAIL
Command [cpanm --reinstall --verbose NCBIx::eUtils::GeneAliases] terminated with exit code 1 ($? = 256) under the following perl environment:
Command terminated with non-zero status.
Current perl:
Name: perl-blead
Path: /home/ryan/perl5/perlbrew/perls/perl-blead/bin/perl
Config: -de -Dprefix=/home/ryan/perl5/perlbrew/perls/perl-blead -Dusedevel -Aeval:scriptdir=/home/ryan/perl5/perlbrew/perls/perl-blead/bin
Compiled at: Mar 30 2017 03:10:09
perlbrew:
version: 0.78
ENV:
PERLBREW_ROOT: /home/ryan/perl5/perlbrew
PERLBREW_HOME: /home/ryan/.perlbrew
PERLBREW_PATH: /home/ryan/perl5/perlbrew/bin:/home/ryan/perl5/perlbrew/perls/perl-blead/bin
PERLBREW_MANPATH: /home/ryan/perl5/perlbrew/perls/perl-blead/man
Reference in a new issue View git blame Copy permalink