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

581 lines
30 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/1493232646.7517
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 SIOC () on cpanmetadb ...
Unpacking SIOC-v1.0.0.tar.gz
--> Working on SIOC
Fetching http://www.cpan.org/authors/id/G/GE/GEEWIZ/SIOC-v1.0.0.tar.gz ... OK
SIOC-v1.0.0/
SIOC-v1.0.0/Changes
SIOC-v1.0.0/lib/
SIOC-v1.0.0/lib/SIOC/
SIOC-v1.0.0/lib/SIOC/Community.pm
SIOC-v1.0.0/lib/SIOC/Container.pm
SIOC-v1.0.0/lib/SIOC/Exporter.pm
SIOC-v1.0.0/lib/SIOC/Forum.pm
SIOC-v1.0.0/lib/SIOC/Item.pm
SIOC-v1.0.0/lib/SIOC/Post.pm
SIOC-v1.0.0/lib/SIOC/Role.pm
SIOC-v1.0.0/lib/SIOC/Site.pm
SIOC-v1.0.0/lib/SIOC/Space.pm
SIOC-v1.0.0/lib/SIOC/Thread.pm
SIOC-v1.0.0/lib/SIOC/User.pm
SIOC-v1.0.0/lib/SIOC/Usergroup.pm
SIOC-v1.0.0/lib/SIOC.pm
SIOC-v1.0.0/Makefile.PL
SIOC-v1.0.0/MANIFEST
SIOC-v1.0.0/META.yml
SIOC-v1.0.0/README
SIOC-v1.0.0/t/
SIOC-v1.0.0/t/00-boilerplate.t
SIOC-v1.0.0/t/00-pod-coverage.t
SIOC-v1.0.0/t/00-pod.t
SIOC-v1.0.0/t/05-perlcritic.t
SIOC-v1.0.0/t/10-load.t
SIOC-v1.0.0/t/20-sioc_base.t
SIOC-v1.0.0/t/21-sioc_community.t
SIOC-v1.0.0/t/21-sioc_container.t
SIOC-v1.0.0/t/21-sioc_forum.t
SIOC-v1.0.0/t/21-sioc_item.t
SIOC-v1.0.0/t/21-sioc_post.t
SIOC-v1.0.0/t/21-sioc_role.t
SIOC-v1.0.0/t/21-sioc_site.t
SIOC-v1.0.0/t/21-sioc_space.t
SIOC-v1.0.0/t/21-sioc_thread.t
SIOC-v1.0.0/t/21-sioc_user.t
SIOC-v1.0.0/t/21-sioc_usergroup.t
Entering SIOC-v1.0.0
Checking configure dependencies from META.yml
Running Makefile.PL
Configuring SIOC-v1.0.0 ... Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for SIOC
Writing MYMETA.yml and MYMETA.json
Checking dependencies from MYMETA.json ...
Checking if you have ExtUtils::MakeMaker 0 ... Yes (7.24)
Checking if you have Moose 0 ... Yes (2.2004)
Checking if you have version 0 ... Yes (0.9918)
Checking if you have Readonly 0 ... Yes (2.05)
Checking if you have Test::More 0 ... Yes (1.302078)
Checking if you have Template::Provider::FromDATA 0 ... Yes (0.13)
Checking if you have Template 0 ... Yes (2.27)
Checking if you have MooseX::AttributeHelpers 0 ... Yes (0.25)
OK
Building and testing SIOC-v1.0.0 ... cp lib/SIOC/Thread.pm blib/lib/SIOC/Thread.pm
cp lib/SIOC/Post.pm blib/lib/SIOC/Post.pm
cp lib/SIOC/Container.pm blib/lib/SIOC/Container.pm
cp lib/SIOC/Forum.pm blib/lib/SIOC/Forum.pm
cp lib/SIOC.pm blib/lib/SIOC.pm
cp lib/SIOC/Usergroup.pm blib/lib/SIOC/Usergroup.pm
cp lib/SIOC/Community.pm blib/lib/SIOC/Community.pm
cp lib/SIOC/User.pm blib/lib/SIOC/User.pm
cp lib/SIOC/Role.pm blib/lib/SIOC/Role.pm
cp lib/SIOC/Exporter.pm blib/lib/SIOC/Exporter.pm
cp lib/SIOC/Space.pm blib/lib/SIOC/Space.pm
cp lib/SIOC/Site.pm blib/lib/SIOC/Site.pm
cp lib/SIOC/Item.pm blib/lib/SIOC/Item.pm
Manifying 13 pod documents
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 SIOC v1.0.0, Perl 5.026000, /home/ryan/perl5/perlbrew/perls/perl-blead/bin/perl5.26.0
t/00-boilerplate.t ..... ok
t/00-pod-coverage.t .... ok
t/00-pod.t ............. ok
t/05-perlcritic.t ...... skipped: Author test. Set $ENV{TEST_AUTHOR} to a true value to run.
t/10-load.t ............ ok
"my" variable $s masks earlier declaration in same statement at
t/20-sioc_base.t line 32 (#1)
(W misc) A "my", "our" or "state" variable has been redeclared in the
current scope or statement, effectively eliminating all access to the
previous instance. This is almost always a typographical error. Note
that the earlier variable will still exist until the end of the scope
or until all closure references to it are destroyed.
"my" variable $PACKAGE masks earlier declaration in same scope at
t/20-sioc_base.t line 32 (#1)
"my" variable $s masks earlier declaration in same scope at t/20-sioc_base.t
line 33 (#1)
"my" variable $s masks earlier declaration in same scope at t/20-sioc_base.t
line 34 (#1)
syntax error at t/20-sioc_base.t line 19, near "fill_template set_template_vars )"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/20-sioc_base.t line 21.
syntax error at t/20-sioc_base.t line 35, near "}"
Execution of t/20-sioc_base.t aborted due to compilation errors (#2)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/20-sioc_base.t line 19, near "fill_template set_template_vars )"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/20-sioc_base.t line 21.
syntax error at t/20-sioc_base.t line 35, near "}"
Execution of t/20-sioc_base.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/20-sioc_base.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
"my" variable $s masks earlier declaration in same statement at
t/21-sioc_community.t line 30 (#1)
(W misc) A "my", "our" or "state" variable has been redeclared in the
current scope or statement, effectively eliminating all access to the
previous instance. This is almost always a typographical error. Note
that the earlier variable will still exist until the end of the scope
or until all closure references to it are destroyed.
"my" variable $PACKAGE masks earlier declaration in same scope at
t/21-sioc_community.t line 30 (#1)
"my" variable $s masks earlier declaration in same scope at
t/21-sioc_community.t line 31 (#1)
"my" variable $s masks earlier declaration in same scope at
t/21-sioc_community.t line 32 (#1)
syntax error at t/21-sioc_community.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_community.t line 19.
syntax error at t/21-sioc_community.t line 33, near "}"
Execution of t/21-sioc_community.t aborted due to compilation errors (#2)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_community.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_community.t line 19.
syntax error at t/21-sioc_community.t line 33, near "}"
Execution of t/21-sioc_community.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_community.t ..
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_container.t line 18, near "add_subscriber )"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_container.t line 20.
Execution of t/21-sioc_container.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_container.t line 18, near "add_subscriber )"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_container.t line 20.
Execution of t/21-sioc_container.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_container.t ..
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_forum.t line 17, near "$subroutine qw( new host add_moderator add_scope )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_forum.t line 19.
Execution of t/21-sioc_forum.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_forum.t line 17, near "$subroutine qw( new host add_moderator add_scope )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_forum.t line 19.
Execution of t/21-sioc_forum.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_forum.t ......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_item.t line 19, near "previous_by_date next_by_date previous_version next_version)"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_item.t line 21.
Execution of t/21-sioc_item.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_item.t line 19, near "previous_by_date next_by_date previous_version next_version)"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_item.t line 21.
Execution of t/21-sioc_item.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_item.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_post.t line 18, near "get_attachment add_related add_sibling note reply_count)"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_post.t line 20.
Execution of t/21-sioc_post.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_post.t line 18, near "get_attachment add_related add_sibling note reply_count)"
(Might be a runaway multi-line () string starting on line 17)
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_post.t line 20.
Execution of t/21-sioc_post.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_post.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_role.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_role.t line 19.
Execution of t/21-sioc_role.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_role.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_role.t line 19.
Execution of t/21-sioc_role.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_role.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
"my" variable $s masks earlier declaration in same statement at
t/21-sioc_site.t line 30 (#1)
(W misc) A "my", "our" or "state" variable has been redeclared in the
current scope or statement, effectively eliminating all access to the
previous instance. This is almost always a typographical error. Note
that the earlier variable will still exist until the end of the scope
or until all closure references to it are destroyed.
"my" variable $PACKAGE masks earlier declaration in same scope at
t/21-sioc_site.t line 30 (#1)
"my" variable $s masks earlier declaration in same scope at t/21-sioc_site.t
line 31 (#1)
"my" variable $s masks earlier declaration in same scope at t/21-sioc_site.t
line 32 (#1)
syntax error at t/21-sioc_site.t line 17, near "$subroutine qw( new add_administrator add_forum )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_site.t line 19.
BEGIN not safe after errors--compilation aborted at t/21-sioc_site.t line 36 (#2)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_site.t line 17, near "$subroutine qw( new add_administrator add_forum )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_site.t line 19.
BEGIN not safe after errors--compilation aborted at t/21-sioc_site.t line 36.
# Looks like your test exited with 255 just after 1.
t/21-sioc_site.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_space.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_space.t line 19.
Execution of t/21-sioc_space.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_space.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_space.t line 19.
Execution of t/21-sioc_space.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_space.t ......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_thread.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_thread.t line 19.
Execution of t/21-sioc_thread.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_thread.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_thread.t line 19.
Execution of t/21-sioc_thread.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_thread.t .....
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
"my" variable $s masks earlier declaration in same statement at
t/21-sioc_user.t line 32 (#1)
(W misc) A "my", "our" or "state" variable has been redeclared in the
current scope or statement, effectively eliminating all access to the
previous instance. This is almost always a typographical error. Note
that the earlier variable will still exist until the end of the scope
or until all closure references to it are destroyed.
"my" variable $PACKAGE masks earlier declaration in same scope at
t/21-sioc_user.t line 32 (#1)
"my" variable $s masks earlier declaration in same scope at t/21-sioc_user.t
line 33 (#1)
"my" variable $s masks earlier declaration in same scope at t/21-sioc_user.t
line 34 (#1)
syntax error at t/21-sioc_user.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_user.t line 19.
syntax error at t/21-sioc_user.t line 35, near "}"
Execution of t/21-sioc_user.t aborted due to compilation errors (#2)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_user.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_user.t line 19.
syntax error at t/21-sioc_user.t line 35, near "}"
Execution of t/21-sioc_user.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_user.t .......
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
syntax error at t/21-sioc_usergroup.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_usergroup.t line 19.
Execution of t/21-sioc_usergroup.t aborted due to compilation errors (#1)
(F) Probably means you had a syntax error. Common reasons include:
A keyword is misspelled.
A semicolon is missing.
A comma is missing.
An opening or closing parenthesis is missing.
An opening or closing brace is missing.
A closing quote is missing.
Often there will be another error message associated with the syntax
error giving more information. (Sometimes it helps to turn on -w.)
The error message itself often tells you where it was in the line when
it decided to give up. Sometimes the actual error is several tokens
before this, because Perl is good at understanding random input.
Occasionally the line number may be misleading, and once in a blue moon
the only way to figure out what's triggering the error is to call
perl -c repeatedly, chopping away half the program each time to see
if the error went away. Sort of the cybernetic version of 20 questions.
Uncaught exception from user code:
syntax error at t/21-sioc_usergroup.t line 17, near "$subroutine qw( new )"
Global symbol "$subroutine" requires explicit package name (did you forget to declare "my $subroutine"?) at t/21-sioc_usergroup.t line 19.
Execution of t/21-sioc_usergroup.t aborted due to compilation errors.
# Looks like your test exited with 255 just after 1.
t/21-sioc_usergroup.t ..
Dubious, test returned 255 (wstat 65280, 0xff00)
All 1 subtests passed
Test Summary Report
-------------------
t/20-sioc_base.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_community.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_container.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_forum.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_item.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_post.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_role.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_site.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_space.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_thread.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_user.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
t/21-sioc_usergroup.t (Wstat: 65280 Tests: 1 Failed: 0)
Non-zero exit status: 255
Files=17, Tests=67, 22 wallclock secs ( 0.04 usr 0.00 sys + 3.80 cusr 0.12 csys = 3.96 CPU)
Result: FAIL
Failed 12/17 test programs. 0/67 subtests failed.
Makefile:903: recipe for target 'test_dynamic' failed
make: *** [test_dynamic] Error 255
! Installing SIOC failed. See /home/ryan/.cpanm/work/1493232646.7517/build.log for details. Retry with --force to force install it.
FAIL
Command [cpanm --reinstall --verbose SIOC] 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