This distribution has been tested as part of the cpan-testers
effort to test as many new uploads to CPAN as possible. See
http://testers.cpan.org/
Please cc any replies to cpan-testers@perl.org to keep other
test volunteers informed and to prevent any duplicate effort.
--
Dear Marc Lehmann,
This is a computer-generated error report created automatically by
CPANPLUS, version 0.076. Testers personal comments may appear
at the end of this report.
Thank you for uploading your work to CPAN. However, it appears that
there were some problems testing your distribution.
TEST RESULTS:
Below is the error stack from stage 'make test':
[MSG] [Sun Jan 21 17:53:30 2007] Writing Makefile for Bundle::Perl6
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires 'Coro' version
'0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Exporter::Simple' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Binding' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Classes' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Currying' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires 'Perl6::Form'
version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Gather' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Interpolators' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Parameters' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Placeholders' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Tokener' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Perl6::Variables' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'Scalar::Properties' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:30 2007] Module 'Bundle::Perl6' requires
'UNIVERSAL::exports' version '0.0' to be installed
[MSG] [Sun Jan 21 17:53:34 2007]
Event version 1.08 found, building Event support.
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Coro has a number of configuration options. Due to its maturity, the
defaults that Coro chooses are usually fine, so you can decide to skip
these questions. Only if something went wrong you should select 'n'
here and manually configure Coro, and, of course, report this to the
maintainer :)
Skip further questions and use defaults (y/n)? [y]
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Coro can use a number of methods to implement coroutines at the C
level. The default chosen is based on your current confguration and is
correct in most cases, but you still can chose between these alternatives:
u The unix 'ucontext.h' functions are relatively new and not implemented
or well-tested in older unices. They allow very fast coroutine creation
and reasonably fast switching, and, most importantly, are very stable.
s If the ucontext functions are not working or you don't want
to use them for other reasons you can try a workaround using
setjmp/longjmp/sigaltstack (also standard unix functions). Coroutine
creation is rather slow, but switching is very fast as well (often much
faster than with the ucontext functions). Unfortunately, glibc-2.1 and
below don't even feature a working sigaltstack.
l GNU/Linux. Very old GNU/Linux systems (glibc-2.1 and below) need
this hack. Since it is very linux-specific it is also quite fast and
recommended even for newer versions; when it works, that is (currently
x86 and a few others only. If it compiles, it's usually ok).
i IRIX. For some reason, SGI really does not like to follow the single
unix specification (does that surprise you?), so this workaround might
be needed (it's fast), although [s] and [u] should also work now.
w Microsoft Windows. Try this on Microsoft Windows, although, as there is
no standard on how to do this under windows, this might work only on
cygwin or specific versions of msvc. Your problem.
For most systems, the default chosen should be OK. If you experience
problems then you should experiment with this setting and/or turn off
optimizations (make OPTIMIZE=-O0).
Use which implementation,
<s>etjmp/longjump, <u>context, <i>rix, <l>inux or <w>indows? [s] s
Using setjmp/longjmp/sigaltstack implementation
Trying to detect stack growth direction (for TEST_sigaltstack)
You might see some warnings, this should not concern you.
*****************************************************************************
If the testsuite fails PLEASE provide the following information
to Marc Lehmann <[EMAIL PROTECTED]>: operating system name, version,
architecture name and this string '(skaddr)|(sksize)'. Thanks a lot!
*****************************************************************************
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Per-context stack size factor: Depending on your settings, Coro tries to
share the C stack as much as possible, but sometimes it needs to allocate
a new one. This setting controls the maximum size that gets allocated,
and should not be set too high, as memory and address space still is
wasted even if it's not fully used. The value entered will be multiplied
by sizeof(long), which is usually 4 on 32-bit systems, and 8 on 64-bit
systems.
A setting of 16384 (the default) therefore corresponds to a 64k..128k
stack, which usually is ample space (you might even want to try 8192 or
lower if your program creates many coroutines).
On systems supporting mmap and dynamic memory management, the actual
memory usually gets allocated on demand, but with many large stacks you
can still run out of address space on your typical 32 bit platform.
Some perls (mostly threaded ones and perl compiled under linux 2.6) and
some programs (inefficient regexes can use a lot of stack space) may
need much, much more: If Coro segfaults with weird backtraces (e.g. in a
function prologue) or in t/10_bugs.t, you might want to increase this to
65536 or more.
The default should be fine.
C stack size factor? [16384] 16384
using a stacksize of 16384 * sizeof(long)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Coro can optionally put a guard area before each stack segment. When the
stack is too small and the access is not too far outside the stack (i.e.
within the guard area), then the program will safely segfault instead of
running into other data. The cost is some additional overhead with is
usually negligible, and extra use of address space.
The guard area size currently needs to be specified in pages (typical
pagesizes are 4k and 8k). The guard area is only enabled on a few
hardcoded architectures and is ignored on others. The actual preprocessor
expression disables this feature if:
!__i386 && !__x86_64 && !__powerpc && !__m68k
&& !__alpha && !__mips && !__sparc64
The default, as usual, should be just fine.
Number of guard pages (0 disables)? [4] 4
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Coro can tell valgrind about its stacks and so reduce spurious warnings
where valgrind would otherwise complain about possible stack switches.
Enabling this does not incur visible runtime or memory overhead, but it
requires that you have the <valgrind/valgrind.h> header file available.
Valgrind support is completely optional, so the default of disabling it is
the safe choice.
Enable valgrind support (y/n)? [n] n
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Coro can use (or even trick) some perl functions into doing what it needs
instead of relying on (some) of its own functions. This might increase
chances that it compiles and works, but it could just as well result in
memory leaks, crashes or silent data corruption. It certainly does result
in slightly slower speed and higher memory consumption, though, so you
should enable it only as a last resort.
Prefer perl functions over coro functions (y/n)? [n] n
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Writing Makefile for Coro::State
Writing Makefile for Coro::Event
Writing Makefile for Coro
[MSG] [Sun Jan 21 17:53:42 2007] cp Coro/Select.pm blib/lib/Coro/Select.pm
cp Coro/State.pm blib/lib/Coro/State.pm
cp Coro/RWLock.pm blib/lib/Coro/RWLock.pm
cp Coro/LWP.pm blib/lib/Coro/LWP.pm
cp Coro/Semaphore.pm blib/lib/Coro/Semaphore.pm
cp Coro/Timer.pm blib/lib/Coro/Timer.pm
cp Coro/CoroAPI.h blib/lib/Coro/CoroAPI.h
cp Coro.pm blib/lib/Coro.pm
cp Coro/Signal.pm blib/lib/Coro/Signal.pm
cp Coro/SemaphoreSet.pm blib/lib/Coro/SemaphoreSet.pm
cp Coro/Util.pm blib/lib/Coro/Util.pm
cp Coro/AIO.pm blib/lib/Coro/AIO.pm
cp Coro/Handle.pm blib/lib/Coro/Handle.pm
cp Coro/Specific.pm blib/lib/Coro/Specific.pm
cp Coro/Socket.pm blib/lib/Coro/Socket.pm
cp Coro/Channel.pm blib/lib/Coro/Channel.pm
cp Coro/MakeMaker.pm blib/lib/Coro/MakeMaker.pm
Skip ../blib/lib/Coro/SemaphoreSet.pm (unchanged)
Skip ../blib/lib/Coro/MakeMaker.pm (unchanged)
Skip ../blib/lib/Coro/Semaphore.pm (unchanged)
Skip ../blib/lib/Coro/AIO.pm (unchanged)
Skip ../blib/lib/Coro/Timer.pm (unchanged)
Skip ../blib/lib/Coro/Socket.pm (unchanged)
Skip ../blib/lib/Coro/State.pm (unchanged)
Skip ../blib/lib/Coro/RWLock.pm (unchanged)
Skip ../blib/lib/Coro/Channel.pm (unchanged)
Skip ../blib/lib/Coro/Signal.pm (unchanged)
Skip ../blib/lib/Coro/Util.pm (unchanged)
Skip ../blib/lib/Coro/Handle.pm (unchanged)
Skip ../blib/lib/Coro/Specific.pm (unchanged)
Skip ../blib/lib/Coro/LWP.pm (unchanged)
Skip ../blib/lib/Coro/Select.pm (unchanged)
/Users/elliot/opt/perl/perl-5.8/bin/perl
/Volumes/Home/elliot/opt/perl/perl-5.8/lib/5.8.8/ExtUtils/xsubpp -typemap
/Users/elliot/opt/perl/perl-5.8/lib/5.8.8/ExtUtils/typemap -typemap typemap
State.xs > State.xsc && mv State.xsc State.c
cc -c -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe
-Wdeclaration-after-statement -O3 -DVERSION=\"3.0\" -DXS_VERSION=\"3.0\"
"-I/Users/elliot/opt/perl/perl-5.8/lib/5.8.8/darwin-2level/CORE" -DHAVE_MMAP
-DCORO_SJLJ -DSTACKSIZE=16384 -DSTACKGUARD=4 State.c
State.xs:193:1: warning: "PRIO_MAX" redefined
In file included from /usr/include/sys/wait.h:111,
from /usr/include/stdlib.h:64,
from libcoro/coro.c:58,
from State.xs:1:
/usr/include/sys/resource.h:110:1: warning: this is the location of the
previous definition
State.xs:198:1: warning: "PRIO_MIN" redefined
/usr/include/sys/resource.h:109:1: warning: this is the location of the
previous definition
State.xs: In function âcoro_state_destroyâ:
State.xs:855: warning: ISO C90 forbids mixed declarations and code
State.xs: In function âprepare_scheduleâ:
State.xs:1031: warning: ISO C90 forbids mixed declarations and code
Running Mkbootstrap for Coro::State ()
chmod 644 State.bs
rm -f ../blib/arch/auto/Coro/State/State.bundle
env MACOSX_DEPLOYMENT_TARGET=10.4 cc -bundle -undefined dynamic_lookup State.o
-o ../blib/arch/auto/Coro/State/State.bundle \
\
chmod 755 ../blib/arch/auto/Coro/State/State.bundle
cp State.bs ../blib/arch/auto/Coro/State/State.bs
chmod 644 ../blib/arch/auto/Coro/State/State.bs
Manifying ../blib/man3/Coro::SemaphoreSet.3
Manifying ../blib/man3/Coro::Semaphore.3
Manifying ../blib/man3/Coro::MakeMaker.3
Manifying ../blib/man3/Coro::Timer.3
Manifying ../blib/man3/Coro::AIO.3
Manifying ../blib/man3/Coro::State.3
Manifying ../blib/man3/Coro::Socket.3
Manifying ../blib/man3/Coro::RWLock.3
Manifying ../blib/man3/Coro::Util.3
Manifying ../blib/man3/Coro::Signal.3
Manifying ../blib/man3/Coro::Channel.3
Manifying ../blib/man3/Coro::Specific.3
Manifying ../blib/man3/Coro::Handle.3
Manifying ../blib/man3/Coro::LWP.3
Manifying ../blib/man3/Coro::Select.3
cp Event.pm ../blib/lib/Coro/Event.pm
/Users/elliot/opt/perl/perl-5.8/bin/perl
/Volumes/Home/elliot/opt/perl/perl-5.8/lib/5.8.8/ExtUtils/xsubpp -typemap
/Users/elliot/opt/perl/perl-5.8/lib/5.8.8/ExtUtils/typemap Event.xs >
Event.xsc && mv Event.xsc Event.c
cc -c
-I/Volumes/Home/elliot/opt/perl/perl-5.8/lib/site_perl/5.8.8/darwin-2level/Event
-fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe
-Wdeclaration-after-statement -O3 -DVERSION=\"2.0\" -DXS_VERSION=\"2.0\"
"-I/Users/elliot/opt/perl/perl-5.8/lib/5.8.8/darwin-2level/CORE" -DHAVE_MMAP
-DCORO_SJLJ -DSTACKSIZE=16384 -DSTACKGUARD=4 Event.c
Running Mkbootstrap for Coro::Event ()
chmod 644 Event.bs
rm -f ../blib/arch/auto/Coro/Event/Event.bundle
env MACOSX_DEPLOYMENT_TARGET=10.4 cc -bundle -undefined dynamic_lookup Event.o
-o ../blib/arch/auto/Coro/Event/Event.bundle \
\
chmod 755 ../blib/arch/auto/Coro/Event/Event.bundle
cp Event.bs ../blib/arch/auto/Coro/Event/Event.bs
chmod 644 ../blib/arch/auto/Coro/Event/Event.bs
Manifying ../blib/man3/Coro::Event.3
Manifying blib/man3/Coro.3
[ERROR] [Sun Jan 21 17:53:45 2007] MAKE TEST failed: PERL_DL_NONLAZY=1
/Users/elliot/opt/perl/perl-5.8/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/00_basic.......FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 3-8
Failed 6/8 tests, 25.00% okay
t/01_process.....FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 2-9
Failed 8/9 tests, 11.11% okay
t/02_channel.....FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 2-19
Failed 18/19 tests, 5.26% okay
t/04_rwlock......FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 8-15
Failed 8/15 tests, 46.67% okay
t/05_specific....FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 5-8
Failed 4/8 tests, 50.00% okay
t/06_prio........FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 2-10
Failed 9/10 tests, 10.00% okay
t/07_eval........FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 2-5
Failed 4/5 tests, 20.00% okay
t/08_join........FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 3-10
Failed 8/10 tests, 20.00% okay
t/10_bugs........FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 2-3
Failed 2/3 tests, 33.33% okay
t/11_deadlock....FATAL: unable to mmap stack for coroutine: Invalid argument
Confused test output: test 3 answered after test 3
FATAL: unable to mmap stack for coroutine: Invalid argument
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 2, 5
Failed 2/5 tests, 60.00% okay
Failed Test Stat Wstat Total Fail List of Failed
-------------------------------------------------------------------------------------------------------------------------------------
t/00_basic.t 1 256 8 12 3-8
t/01_process.t 1 256 9 16 2-9
t/02_channel.t 1 256 19 36 2-19
t/04_rwlock.t 1 256 15 16 8-15
t/05_specific.t 1 256 8 8 5-8
t/06_prio.t 1 256 10 18 2-10
t/07_eval.t 1 256 5 8 2-5
t/08_join.t 1 256 10 16 3-10
t/10_bugs.t 1 256 3 4 2-3
t/11_deadlock.t 1 256 5 3 2 5
Failed 10/10 test scripts. 69/92 subtests failed.
Files=10, Tests=92, 2 wallclock secs ( 0.41 cusr + 0.20 csys = 0.61 CPU)
Failed 10/10 test programs. 69/92 subtests failed.
PREREQUISITES:
Here is a list of prerequisites you specified and versions we
managed to load:
AnyEvent 2.51
Event 1.08
IO::AIO 2.31
Scalar::Util 1.19
******************************** NOTE ********************************
The comments above are created mechanically, possibly without manual
checking by the sender. As there are many people performing automatic
tests on each upload to CPAN, it is likely that you will receive
identical messages about the same problem.
If you believe that the message is mistaken, please reply to the first
one with correction and/or additional informations, and do not take
it personally. We appreciate your patience. :)
**********************************************************************
Additional comments:
--
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=darwin, osvers=8.7.0, archname=darwin-2level
uname='darwin spinynorman.local 8.7.0 darwin kernel version 8.7.0: fri may
26 15:20:53 pdt 2006; root:xnu-792.6.76.obj~1release_ppc power macintosh
powerpc '
config_args=''
hint=previous, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='cc', ccflags ='-fno-common -DPERL_DARWIN -no-cpp-precomp
-fno-strict-aliasing -pipe -Wdeclaration-after-statement',
optimize='-O3',
cppflags='-no-cpp-precomp -fno-common -DPERL_DARWIN -no-cpp-precomp
-fno-strict-aliasing -pipe -Wdeclaration-after-statement -fno-common
-DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe
-Wdeclaration-after-statement -fno-common -DPERL_DARWIN -no-cpp-precomp
-fno-strict-aliasing -pipe -Wdeclaration-after-statement'
ccversion='', gccversion='4.0.1 (Apple Computer, Inc. build 5341)',
gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=4321
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='env MACOSX_DEPLOYMENT_TARGET=10.4 cc', ldflags =''
libpth=/usr/lib
libs=-ldbm -ldl -lm -lc
perllibs=-ldl -lm -lc
libc=/usr/lib/libc.dylib, so=dylib, useshrplib=true, libperl=libperl.dylib
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags=' -bundle -undefined dynamic_lookup'
