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

303 lines
32 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/1493631103.2560
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 Ingres::Utility::IIMonitor () on cpanmetadb ...
Unpacking Ingres-Utility-IIMonitor-0.13.tar.gz
--> Working on Ingres::Utility::IIMonitor
Fetching http://www.cpan.org/authors/id/W/WO/WORM/Ingres-Utility-IIMonitor-0.13.tar.gz ... OK
Ingres-Utility-IIMonitor-0.13/
Ingres-Utility-IIMonitor-0.13/META.yml
Ingres-Utility-IIMonitor-0.13/Changes
Ingres-Utility-IIMonitor-0.13/t/
Ingres-Utility-IIMonitor-0.13/t/pod-coverage.t
Ingres-Utility-IIMonitor-0.13/t/pod.t
Ingres-Utility-IIMonitor-0.13/t/00.load.t
Ingres-Utility-IIMonitor-0.13/t/perlcritic.t
Ingres-Utility-IIMonitor-0.13/MANIFEST
Ingres-Utility-IIMonitor-0.13/lib/
Ingres-Utility-IIMonitor-0.13/lib/Ingres/
Ingres-Utility-IIMonitor-0.13/lib/Ingres/Utility/
Ingres-Utility-IIMonitor-0.13/lib/Ingres/Utility/IIMonitor.pm
Ingres-Utility-IIMonitor-0.13/Build.PL
Ingres-Utility-IIMonitor-0.13/Makefile.PL
Ingres-Utility-IIMonitor-0.13/README
Entering Ingres-Utility-IIMonitor-0.13
Checking configure dependencies from META.yml
Checking if you have ExtUtils::Install 1.46 ... Yes (2.04)
Checking if you have Module::Build 0.38 ... Yes (0.4222)
Running Build.PL
Configuring Ingres-Utility-IIMonitor-0.13 ... Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Ingres-Utility-IIMonitor' version '0.13'
Checking dependencies from MYMETA.json ...
Checking if you have Test::More 0 ... Yes (1.302083)
Checking if you have Expect::Simple 0 ... Yes (0.04)
OK
Building and testing Ingres-Utility-IIMonitor-0.13 ... Building Ingres-Utility-IIMonitor
# Testing Ingres::Utility::IIMonitor 0.13
t/00.load.t ....... ok
# Failed test 'Test::Perl::Critic for "blib/lib/Ingres/Utility/IIMonitor.pm"'
# at /home/ryan/perl5/perlbrew/perls/perl-blead/lib/site_perl/5.26.0/Test/Perl/Critic.pm line 104.
#
# Subroutine prototypes used at line 84, column 1. See page 194 of PBP. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 85, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 86, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 87, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 87, column 18. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 87, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 88, column 11. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 88, column 18. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 89, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 90, column 11. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 96, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 98, column 14. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 101, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 101, column 5. 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 101, column 20. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 102, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 102, column 5. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5)
# Subroutine "new" called using indirect syntax at line 102, column 21. See page 349 of PBP. (Severity: 5)
# Use of low precedence operators is not allowed at line 109, column 11. Replace low precedence operators with the high precedence substitutes. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 110, column 9. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 110, column 9. 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 110, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 111, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 129, column 1. (no explanation). (Severity: 5)
# Subroutine prototypes used at line 129, column 1. See page 194 of PBP. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 130, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 131, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 132, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 133, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 134, column 17. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 141, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 141, column 15. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 141, column 15. 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 142, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 142, column 34. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 143, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 143, column 18. (no explanation). (Severity: 5)
# Method invocation should use "()" at line 143, column 22. Use "->MethodName()" instead of "->MethodName". (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 144, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 145, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 147, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 147, column 30. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 148, column 20. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 164, column 1. (no explanation). (Severity: 5)
# Subroutine prototypes used at line 164, column 1. See page 194 of PBP. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 165, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 166, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 167, column 11. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 170, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 171, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 172, column 17. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 178, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 178, column 15. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 178, column 15. 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 179, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 179, column 33. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 180, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 180, column 18. (no explanation). (Severity: 5)
# Method invocation should use "()" at line 180, column 22. Use "->MethodName()" instead of "->MethodName". (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 181, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 182, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 184, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 184, column 30. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 185, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 196, column 1. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 197, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 198, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 198, column 15. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 198, column 15. 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 199, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 200, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 200, column 18. (no explanation). (Severity: 5)
# Method invocation should use "()" at line 200, column 22. Use "->MethodName()" instead of "->MethodName". (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 201, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 202, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 204, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 204, column 30. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 210, column 1. (no explanation). (Severity: 5)
# Subroutine prototypes used at line 210, column 1. See page 194 of PBP. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 211, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 212, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 213, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 213, column 16. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 214, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 215, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 233, column 1. (no explanation). (Severity: 5)
# Subroutine prototypes used at line 233, column 1. See page 194 of PBP. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 234, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 235, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 236, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 237, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 238, column 9. (no explanation). (Severity: 5)
# Use of low precedence operators is not allowed at line 238, column 32. Replace low precedence operators with the high precedence substitutes. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 239, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 244, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 244, column 19. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 245, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 248, column 13. (no explanation). (Severity: 5)
# Use of low precedence operators is not allowed at line 248, column 33. Replace low precedence operators with the high precedence substitutes. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 249, column 13. (no explanation). (Severity: 5)
# Use of low precedence operators is not allowed at line 249, column 33. Replace low precedence operators with the high precedence substitutes. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 250, column 13. (no explanation). (Severity: 5)
# Use of low precedence operators is not allowed at line 250, column 33. Replace low precedence operators with the high precedence substitutes. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 251, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 255, column 9. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 256, column 13. (no explanation). (Severity: 5)
# Use of low precedence operators is not allowed at line 256, column 34. Replace low precedence operators with the high precedence substitutes. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 257, column 13. (no explanation). (Severity: 5)
# Use of low precedence operators is not allowed at line 257, column 34. Replace low precedence operators with the high precedence substitutes. (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 258, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 263, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 263, column 15. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 263, column 15. 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 264, column 5. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 265, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 265, column 18. (no explanation). (Severity: 5)
# Method invocation should use "()" at line 265, column 22. Use "->MethodName()" instead of "->MethodName". (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 269, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 269, column 5. 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 269, column 25. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 270, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 270, column 5. 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 270, column 25. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 271, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 271, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 272, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 272, column 5. 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 272, column 30. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 273, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 273, column 5. 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 274, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 274, column 5. 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 275, column 12. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 298, column 1. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 299, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 300, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 301, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 302, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 303, column 8. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 306, column 9. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 306, column 9. 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 306, column 38. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 306, column 38. 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 307, column 9. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 307, column 9. 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 308, column 16. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 311, column 11. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 311, column 11. 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 311, column 44. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 311, column 44. 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 312, column 14. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 312, column 14. 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 314, column 17. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 314, column 17. 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 315, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 316, column 37. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 319, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 320, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 322, column 28. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 323, column 52. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 324, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 324, column 37. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 325, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 325, column 37. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 325, column 57. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 326, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 327, column 41. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 328, column 33. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 328, column 42. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 330, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 330, column 35. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 330, column 44. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 336, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 337, column 37. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 340, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 341, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 342, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 343, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 344, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 348, column 16. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 349, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 350, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 352, column 16. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 353, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 354, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 356, column 16. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 357, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 358, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 359, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 361, column 16. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 362, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 362, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 363, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 363, column 19. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 365, column 16. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 366, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 366, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 367, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 367, column 19. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 370, column 13. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 371, column 39. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 372, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 373, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 373, column 29. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 373, column 49. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 374, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 375, column 33. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 376, column 25. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 376, column 34. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 377, column 39. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 377, column 53. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 378, column 34. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 381, column 21. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 381, column 27. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 381, column 36. (no explanation). (Severity: 5)
# Variable, subroutine, and package names have to be in CamelCase at line 386, column 5. (no explanation). (Severity: 5)
# Private Member Data shouldn't be accessed directly at line 386, column 5. 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 387, column 12. (no explanation). (Severity: 5)
t/perlcritic.t ....
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests
t/pod-coverage.t .. ok
t/pod.t ........... ok
Test Summary Report
-------------------
t/perlcritic.t (Wstat: 256 Tests: 1 Failed: 1)
Failed test: 1
Non-zero exit status: 1
Files=4, Tests=4, 3 wallclock secs ( 0.01 usr 0.01 sys + 0.86 cusr 0.06 csys = 0.94 CPU)
Result: FAIL
Failed 1/4 test programs. 1/4 subtests failed.
! Installing Ingres::Utility::IIMonitor failed. See /home/ryan/.cpanm/work/1493631103.2560/build.log for details. Retry with --force to force install it.
FAIL
Command [cpanm --reinstall --verbose Ingres::Utility::IIMonitor] 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