Skip Menu |

This queue is for tickets about the Coro CPAN distribution.

Report information
The Basics
Id: 96714
Status: resolved
Priority: 0/
Queue: Coro

People
Owner: MLEHMANN [...] cpan.org
Requestors: MARKLE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 6.39
Fixed in: 6.44



Subject: hangs forever on Event support test
================================= ... Skip ../blib/lib/Coro/Storable.pm (unchanged) Warning: Aliases 'is_zombie' and 'is_destroyed' have identical values in State.xs, line 3666 cc -c -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" -DXS_VERSION=\"6.39\" -fPIC "-I/ntfhome/local/lib/perl5/5.20.0/x86_64-linux-thread-multi- ld/CORE" -DCORO_ASM -DCORO_STACKSIZE=16384 -DCORO_GUARDPAGES=4 -DCORO_JIT=1 State.c rm -f ../blib/arch/auto/Coro/State/State.so cc -shared -O2 -L/usr/local/lib -fstack-protector State.o -o ../blib/arch/auto/Coro/State/State.so \ \ chmod 755 ../blib/arch/auto/Coro/State/State.so /ntfhome/local/bin/perl -MExtUtils::Command::MM -e 'cp_nonempty' -- State.bs ../blib/arch/auto/Coro/State/State.bs 644 Manifying ../blib/man3/Coro::AIO.3 Manifying ../blib/man3/Coro::AnyEvent.3 Manifying ../blib/man3/Coro::BDB.3 Manifying ../blib/man3/Coro::Channel.3 Manifying ../blib/man3/Coro::Debug.3 Manifying ../blib/man3/Coro::Handle.3 Manifying ../blib/man3/Coro::Intro.3 Manifying ../blib/man3/Coro::LWP.3 Manifying ../blib/man3/Coro::MakeMaker.3 Manifying ../blib/man3/Coro::RWLock.3 Manifying ../blib/man3/Coro::Select.3 Manifying ../blib/man3/Coro::Semaphore.3 Manifying ../blib/man3/Coro::SemaphoreSet.3 Manifying ../blib/man3/Coro::Signal.3 Manifying ../blib/man3/Coro::Socket.3 Manifying ../blib/man3/Coro::Specific.3 Manifying ../blib/man3/Coro::State.3 Manifying ../blib/man3/Coro::Storable.3 Manifying ../blib/man3/Coro::Timer.3 Manifying ../blib/man3/Coro::Util.3 make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' /ntfhome/local/bin/perl /ntfhome/local/lib/perl5/5.20.0/ExtUtils/xsubpp -typemap /ntfhome/local/lib/perl5/5.20.0/ExtUtils/typemap Event.xs > Event.xsc && mv Event.xsc Event.c Running Mkbootstrap for Coro::Event () cp Event.pm ../blib/lib/Coro/Event.pm chmod 644 Event.bs cc -c -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64-linux- thread-multi-ld/Event -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict- aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" -DXS_VERSION=\"6.39\" -fPIC "-I/ntfhome/local/lib/perl5/5.20.0/x86_64- linux-thread-multi-ld/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 Event.c rm -f ../blib/arch/auto/Coro/Event/Event.so cc -shared -O2 -L/usr/local/lib -fstack-protector Event.o -o ../blib/arch/auto/Coro/Event/Event.so \ \ chmod 755 ../blib/arch/auto/Coro/Event/Event.so /ntfhome/local/bin/perl -MExtUtils::Command::MM -e 'cp_nonempty' -- Event.bs ../blib/arch/auto/Coro/Event/Event.bs 644 Manifying ../blib/man3/Coro::Event.3 make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' /ntfhome/local/bin/perl /ntfhome/local/lib/perl5/5.20.0/ExtUtils/xsubpp -typemap /ntfhome/local/lib/perl5/5.20.0/ExtUtils/typemap EV.xs > EV.xsc && mv EV.xsc EV.c Running Mkbootstrap for Coro::EV () cp EV.pm ../blib/lib/Coro/EV.pm chmod 644 EV.bs cc -c -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64-linux- thread-multi-ld/EV -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64- linux-thread-multi-ld -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict- aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" -DXS_VERSION=\"6.39\" -fPIC "-I/ntfhome/local/lib/perl5/5.20.0/x86_64- linux-thread-multi-ld/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 EV.c rm -f ../blib/arch/auto/Coro/EV/EV.so cc -shared -O2 -L/usr/local/lib -fstack-protector EV.o -o ../blib/arch/auto/Coro/EV/EV.so \ \ ch::MM -e 'cp_nonempty' -- EV.bs ../blib/arch/auto/Coro/EV/EV.bs 644 Manifying ../blib/man3/Coro::EV.3 make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' Manifying blib/man3/Coro.3 MLEHMANN/Coro-6.39.tar.gz /usr/bin/make -j16 -j16 -- OK Running make test make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' Running Mkbootstrap for Coro::State () chmod 644 State.bs make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' Running Mkbootstrap for Coro::Event () chmod 644 Event.bs make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' Running Mkbootstrap for Coro::EV () chmod 644 EV.bs make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' PERL_DL_NONLAZY=1 /ntfhome/local/bin/perl "-MExtUtils::Command::MM" "- MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00_basic.t .......... ok t/01_process.t ........ ok t/02_channel.t ........ ok t/03_channel.t ........ ok t/04_rwlock.t ......... ok t/05_specific.t ....... ok t/06_prio.t ........... ok t/07_eval.t ........... ok t/08_join.t ........... ok t/10_bugs.t ........... ok t/11_deadlock.t ....... ok t/12_exit.t ........... ok t/13_diewarn.t ........ ok t/14_load.t ........... ok t/15_semaphore.t ...... ok t/16_signal.t ......... ok t/17_rouse.t .......... ok t/18_winder.t ......... ok t/19_handle.t ......... ok t/20_mutual_cancel.t .. ok All tests successful. Files=20, Tests=196, 2 wallclock secs ( 0.10 usr 0.13 sys + 0.93 cusr 0.32 csys = 1.48 CPU) Result: PASS make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' No tests defined for Coro::State extension. make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' PERL_DL_NONLAZY=1 /ntfhome/local/bin/perl "-MExtUtils::Command::MM" "- MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, '../blib/lib', '../blib/arch')" t/*.t t/00_basic.t .... ok t/01_unblock.t .. 1/12 [HANGS FOREVER] ==================================== sre@tst1.ntf.cftdev1 /tmp/cpan/sources/authors/id/M/ML/MLEHMANN/Coro- 6.39/Event 2014-06-25 11:55:48 Wed $ perl -Mblib t/01_unblock.t 1..12 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 [HANGS FOREVER]
I removed all the Event CPAN libraries, and the rest of Coro installed fine. Does Event.pm depend on libevent? Maybe this is due to some untested bug in Event.pm. The version of libevent on this Oracle Entrprise Lame-o 5.8 machine is 1.4.13, which is probably circa 2006. Would it be a good idea to make Event support optional as one of the configuration questions, even if Event.pm is installed? Thanks. Mark
Subject: Re: [rt.cpan.org #96714] hangs forever on Event support test
Date: Thu, 26 Jun 2014 00:26:57 +0200
To: Mark Hedges via RT <bug-Coro [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
Hi! Please send your bug report it to the official contact/author address for the module in question (or send it to rt.cpan.org@schmorp.de, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. Why is this necessary? rt.cpan.org has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring rt.cpan.org is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss potentially vital bug reports such as yours (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the rt.cpan.org providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the rt.cpan.org providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects search.cpan.org and maybe similar services. (Many people confuse rt.cpan.org with search.cpan.org for some reason). 2. It doesn't even work (there are still links to rt.cpan.org displayed). 3. Even if search.cpan.org does no longer display the link, it doesn't actually affect rt.cpan.org (and tests have shown that people go to rt.cpan.org regardless) Even *iff* rt.cpan.org would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like rt.cpan.org comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de> Last updated: 2012-04-22
On 2014-06-25 15:02:49, MARKLE wrote: Show quoted text
> ================================= > ... > Skip ../blib/lib/Coro/Storable.pm (unchanged) > Warning: Aliases 'is_zombie' and 'is_destroyed' have identical values > in State.xs, line 3666 > cc -c -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict-aliasing -pipe > -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" -DXS_VERSION=\"6.39\" > -fPIC "-I/ntfhome/local/lib/perl5/5.20.0/x86_64-linux-thread-multi- > ld/CORE" -DCORO_ASM -DCORO_STACKSIZE=16384 -DCORO_GUARDPAGES=4 > -DCORO_JIT=1 State.c > rm -f ../blib/arch/auto/Coro/State/State.so > cc -shared -O2 -L/usr/local/lib -fstack-protector State.o -o > ../blib/arch/auto/Coro/State/State.so \ > \ > > chmod 755 ../blib/arch/auto/Coro/State/State.so > /ntfhome/local/bin/perl -MExtUtils::Command::MM -e 'cp_nonempty' -- > State.bs ../blib/arch/auto/Coro/State/State.bs 644 > Manifying ../blib/man3/Coro::AIO.3 > Manifying ../blib/man3/Coro::AnyEvent.3 > Manifying ../blib/man3/Coro::BDB.3 > Manifying ../blib/man3/Coro::Channel.3 > Manifying ../blib/man3/Coro::Debug.3 > Manifying ../blib/man3/Coro::Handle.3 > Manifying ../blib/man3/Coro::Intro.3 > Manifying ../blib/man3/Coro::LWP.3 > Manifying ../blib/man3/Coro::MakeMaker.3 > Manifying ../blib/man3/Coro::RWLock.3 > Manifying ../blib/man3/Coro::Select.3 > Manifying ../blib/man3/Coro::Semaphore.3 > Manifying ../blib/man3/Coro::SemaphoreSet.3 > Manifying ../blib/man3/Coro::Signal.3 > Manifying ../blib/man3/Coro::Socket.3 > Manifying ../blib/man3/Coro::Specific.3 > Manifying ../blib/man3/Coro::State.3 > Manifying ../blib/man3/Coro::Storable.3 > Manifying ../blib/man3/Coro::Timer.3 > Manifying ../blib/man3/Coro::Util.3 > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > /ntfhome/local/bin/perl > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/xsubpp -typemap > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/typemap Event.xs > Event.xsc > && mv Event.xsc Event.c > Running Mkbootstrap for Coro::Event () > cp Event.pm ../blib/lib/Coro/Event.pm > chmod 644 Event.bs > cc -c -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64-linux- > thread-multi-ld/Event -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict- > aliasing -pipe -fstack-protector -I/usr/local/include > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" > -DXS_VERSION=\"6.39\" -fPIC "-I/ntfhome/local/lib/perl5/5.20.0/x86_64- > linux-thread-multi-ld/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 Event.c > rm -f ../blib/arch/auto/Coro/Event/Event.so > cc -shared -O2 -L/usr/local/lib -fstack-protector Event.o -o > ../blib/arch/auto/Coro/Event/Event.so \ > \ > > chmod 755 ../blib/arch/auto/Coro/Event/Event.so > /ntfhome/local/bin/perl -MExtUtils::Command::MM -e 'cp_nonempty' -- > Event.bs ../blib/arch/auto/Coro/Event/Event.bs 644 > Manifying ../blib/man3/Coro::Event.3 > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > /ntfhome/local/bin/perl > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/xsubpp -typemap > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/typemap EV.xs > EV.xsc && mv > EV.xsc EV.c > Running Mkbootstrap for Coro::EV () > cp EV.pm ../blib/lib/Coro/EV.pm > chmod 644 EV.bs > cc -c -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64-linux- > thread-multi-ld/EV -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64- > linux-thread-multi-ld -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict- > aliasing -pipe -fstack-protector -I/usr/local/include > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" > -DXS_VERSION=\"6.39\" -fPIC "-I/ntfhome/local/lib/perl5/5.20.0/x86_64- > linux-thread-multi-ld/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 EV.c > rm -f ../blib/arch/auto/Coro/EV/EV.so > cc -shared -O2 -L/usr/local/lib -fstack-protector EV.o -o > ../blib/arch/auto/Coro/EV/EV.so \ > \ > > ch::MM -e 'cp_nonempty' -- > EV.bs ../blib/arch/auto/Coro/EV/EV.bs 644 > Manifying ../blib/man3/Coro::EV.3 > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > Manifying blib/man3/Coro.3 > MLEHMANN/Coro-6.39.tar.gz > /usr/bin/make -j16 -j16 -- OK > Running make test > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > Running Mkbootstrap for Coro::State () > chmod 644 State.bs > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > Running Mkbootstrap for Coro::Event () > chmod 644 Event.bs > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > Running Mkbootstrap for Coro::EV () > chmod 644 EV.bs > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > PERL_DL_NONLAZY=1 /ntfhome/local/bin/perl "-MExtUtils::Command::MM" "- > MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, > 'blib/lib', 'blib/arch')" t/*.t > t/00_basic.t .......... ok > t/01_process.t ........ ok > t/02_channel.t ........ ok > t/03_channel.t ........ ok > t/04_rwlock.t ......... ok > t/05_specific.t ....... ok > t/06_prio.t ........... ok > t/07_eval.t ........... ok > t/08_join.t ........... ok > t/10_bugs.t ........... ok > t/11_deadlock.t ....... ok > t/12_exit.t ........... ok > t/13_diewarn.t ........ ok > t/14_load.t ........... ok > t/15_semaphore.t ...... ok > t/16_signal.t ......... ok > t/17_rouse.t .......... ok > t/18_winder.t ......... ok > t/19_handle.t ......... ok > t/20_mutual_cancel.t .. ok > All tests successful. > Files=20, Tests=196, 2 wallclock secs ( 0.10 usr 0.13 sys + 0.93 > cusr 0.32 csys = 1.48 CPU) > Result: PASS > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > No tests defined for Coro::State extension. > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > PERL_DL_NONLAZY=1 /ntfhome/local/bin/perl "-MExtUtils::Command::MM" "- > MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, > '../blib/lib', '../blib/arch')" t/*.t > t/00_basic.t .... ok > t/01_unblock.t .. 1/12 > [HANGS FOREVER] > ==================================== > sre@tst1.ntf.cftdev1 /tmp/cpan/sources/authors/id/M/ML/MLEHMANN/Coro- > 6.39/Event > 2014-06-25 11:55:48 Wed $ perl -Mblib t/01_unblock.t > 1..12 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > [HANGS FOREVER]
I see this problem also, exactly at this point, but only on a Debian/wheezy system and with perl 5.20.1 which is compiled with -Duselongdouble. A normal 5.20.1 is fine, and a 5.20.1+uselongdouble on FreeBSD also shows no problems. Another indication: there's no PASS report with uselongdouble perl visible here (recognizable with a "-ld" suffix in the archname) : http://matrix.cpantesters.org/?dist=Coro%206.43;os=linux;reports=1 and I know that at least Andreas Koenig tests with a lot of uselongduble perls.
On 2015-06-07 09:04:33, SREZIC wrote: Show quoted text
> On 2014-06-25 15:02:49, MARKLE wrote:
> > ================================= > > ... > > Skip ../blib/lib/Coro/Storable.pm (unchanged) > > Warning: Aliases 'is_zombie' and 'is_destroyed' have identical values > > in State.xs, line 3666 > > cc -c -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict-aliasing -pipe > > -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE > > -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" -DXS_VERSION=\"6.39\" > > -fPIC "-I/ntfhome/local/lib/perl5/5.20.0/x86_64-linux-thread-multi- > > ld/CORE" -DCORO_ASM -DCORO_STACKSIZE=16384 -DCORO_GUARDPAGES=4 > > -DCORO_JIT=1 State.c > > rm -f ../blib/arch/auto/Coro/State/State.so > > cc -shared -O2 -L/usr/local/lib -fstack-protector State.o -o > > ../blib/arch/auto/Coro/State/State.so \ > > \ > > > > chmod 755 ../blib/arch/auto/Coro/State/State.so > > /ntfhome/local/bin/perl -MExtUtils::Command::MM -e 'cp_nonempty' -- > > State.bs ../blib/arch/auto/Coro/State/State.bs 644 > > Manifying ../blib/man3/Coro::AIO.3 > > Manifying ../blib/man3/Coro::AnyEvent.3 > > Manifying ../blib/man3/Coro::BDB.3 > > Manifying ../blib/man3/Coro::Channel.3 > > Manifying ../blib/man3/Coro::Debug.3 > > Manifying ../blib/man3/Coro::Handle.3 > > Manifying ../blib/man3/Coro::Intro.3 > > Manifying ../blib/man3/Coro::LWP.3 > > Manifying ../blib/man3/Coro::MakeMaker.3 > > Manifying ../blib/man3/Coro::RWLock.3 > > Manifying ../blib/man3/Coro::Select.3 > > Manifying ../blib/man3/Coro::Semaphore.3 > > Manifying ../blib/man3/Coro::SemaphoreSet.3 > > Manifying ../blib/man3/Coro::Signal.3 > > Manifying ../blib/man3/Coro::Socket.3 > > Manifying ../blib/man3/Coro::Specific.3 > > Manifying ../blib/man3/Coro::State.3 > > Manifying ../blib/man3/Coro::Storable.3 > > Manifying ../blib/man3/Coro::Timer.3 > > Manifying ../blib/man3/Coro::Util.3 > > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > > /ntfhome/local/bin/perl > > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/xsubpp -typemap > > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/typemap Event.xs > > > Event.xsc > > && mv Event.xsc Event.c > > Running Mkbootstrap for Coro::Event () > > cp Event.pm ../blib/lib/Coro/Event.pm > > chmod 644 Event.bs > > cc -c -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64-linux- > > thread-multi-ld/Event -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict- > > aliasing -pipe -fstack-protector -I/usr/local/include > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" > > -DXS_VERSION=\"6.39\" -fPIC "- > > I/ntfhome/local/lib/perl5/5.20.0/x86_64- > > linux-thread-multi-ld/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 Event.c > > rm -f ../blib/arch/auto/Coro/Event/Event.so > > cc -shared -O2 -L/usr/local/lib -fstack-protector Event.o -o > > ../blib/arch/auto/Coro/Event/Event.so \ > > \ > > > > chmod 755 ../blib/arch/auto/Coro/Event/Event.so > > /ntfhome/local/bin/perl -MExtUtils::Command::MM -e 'cp_nonempty' -- > > Event.bs ../blib/arch/auto/Coro/Event/Event.bs 644 > > Manifying ../blib/man3/Coro::Event.3 > > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > > /ntfhome/local/bin/perl > > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/xsubpp -typemap > > /ntfhome/local/lib/perl5/5.20.0/ExtUtils/typemap EV.xs > EV.xsc && > > mv > > EV.xsc EV.c > > Running Mkbootstrap for Coro::EV () > > cp EV.pm ../blib/lib/Coro/EV.pm > > chmod 644 EV.bs > > cc -c -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64-linux- > > thread-multi-ld/EV > > -I/ntfhome/local/lib/perl5/site_perl/5.20.0/x86_64- > > linux-thread-multi-ld -D_REENTRANT -D_GNU_SOURCE -fPIC -fno-strict- > > aliasing -pipe -fstack-protector -I/usr/local/include > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"6.39\" > > -DXS_VERSION=\"6.39\" -fPIC "- > > I/ntfhome/local/lib/perl5/5.20.0/x86_64- > > linux-thread-multi-ld/CORE" -DHAVE_EVENT=1 -DHAVE_EV=1 EV.c > > rm -f ../blib/arch/auto/Coro/EV/EV.so > > cc -shared -O2 -L/usr/local/lib -fstack-protector EV.o -o > > ../blib/arch/auto/Coro/EV/EV.so \ > > \ > > > > ch::MM -e 'cp_nonempty' -- > > EV.bs ../blib/arch/auto/Coro/EV/EV.bs 644 > > Manifying ../blib/man3/Coro::EV.3 > > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > > Manifying blib/man3/Coro.3 > > MLEHMANN/Coro-6.39.tar.gz > > /usr/bin/make -j16 -j16 -- OK > > Running make test > > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > > Running Mkbootstrap for Coro::State () > > chmod 644 State.bs > > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > > Running Mkbootstrap for Coro::Event () > > chmod 644 Event.bs > > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > > Running Mkbootstrap for Coro::EV () > > chmod 644 EV.bs > > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/EV' > > PERL_DL_NONLAZY=1 /ntfhome/local/bin/perl "-MExtUtils::Command::MM" > > "- > > MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, > > 'blib/lib', 'blib/arch')" t/*.t > > t/00_basic.t .......... ok > > t/01_process.t ........ ok > > t/02_channel.t ........ ok > > t/03_channel.t ........ ok > > t/04_rwlock.t ......... ok > > t/05_specific.t ....... ok > > t/06_prio.t ........... ok > > t/07_eval.t ........... ok > > t/08_join.t ........... ok > > t/10_bugs.t ........... ok > > t/11_deadlock.t ....... ok > > t/12_exit.t ........... ok > > t/13_diewarn.t ........ ok > > t/14_load.t ........... ok > > t/15_semaphore.t ...... ok > > t/16_signal.t ......... ok > > t/17_rouse.t .......... ok > > t/18_winder.t ......... ok > > t/19_handle.t ......... ok > > t/20_mutual_cancel.t .. ok > > All tests successful. > > Files=20, Tests=196, 2 wallclock secs ( 0.10 usr 0.13 sys + 0.93 > > cusr 0.32 csys = 1.48 CPU) > > Result: PASS > > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > > No tests defined for Coro::State extension. > > make[1]: Leaving directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Coro' > > make[1]: Entering directory `/tmp/cpan/build/Coro-6.39-RM5cIY/Event' > > PERL_DL_NONLAZY=1 /ntfhome/local/bin/perl "-MExtUtils::Command::MM" > > "- > > MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, > > '../blib/lib', '../blib/arch')" t/*.t > > t/00_basic.t .... ok > > t/01_unblock.t .. 1/12 > > [HANGS FOREVER] > > ==================================== > > sre@tst1.ntf.cftdev1 /tmp/cpan/sources/authors/id/M/ML/MLEHMANN/Coro- > > 6.39/Event > > 2014-06-25 11:55:48 Wed $ perl -Mblib t/01_unblock.t > > 1..12 > > ok 1 > > ok 2 > > ok 3 > > ok 4 > > ok 5 > > ok 6 > > [HANGS FOREVER]
> > I see this problem also, exactly at this point, but only on a > Debian/wheezy system and with perl 5.20.1 which is compiled with > -Duselongdouble. A normal 5.20.1 is fine, and a 5.20.1+uselongdouble > on FreeBSD also shows no problems. Another indication: there's no PASS > report with uselongdouble perl visible here (recognizable with a "-ld" > suffix in the archname) : > http://matrix.cpantesters.org/?dist=Coro%206.43;os=linux;reports=1 and > I know that at least Andreas Koenig tests with a lot of uselongduble > perls.
According to Changes file this was fixed in 6.44.
CC: ;
Subject: Re: [rt.cpan.org #96714] hangs forever on Event support test
Date: Thu, 2 Jul 2015 01:42:24 +0200
To: Slaven_Rezic via RT <bug-Coro [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
On Wed, Jul 01, 2015 at 03:10:34AM -0400, Slaven_Rezic via RT <bug-Coro@rt.cpan.org> wrote: Show quoted text
> According to Changes file this was fixed in 6.44.
Not according to the Changes file I published - where do you get this information from? The problem is that Event silently broke its API without bumping the API version, so the problem persists and can merely be hidden (there is no reasonable way for other modules to test this). In any case, I would really prefer if you would be more helpful and stopped spamming this bugtracker. Your disruptive behaviour really isn't appreciated, or constructive. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schmorp@schmorp.de -=====/_/_//_/\_,_/ /_/\_\
On 2015-07-01 19:42:43, schmorp@schmorp.de wrote: Show quoted text
> On Wed, Jul 01, 2015 at 03:10:34AM -0400, Slaven_Rezic via RT <bug- > Coro@rt.cpan.org> wrote:
> > According to Changes file this was fixed in 6.44.
> > Not according to the Changes file I published - where do you get this > information from?
https://metacpan.org/source/MLEHMANN/Coro-6.46/Changes#L19 contains the terms mentioned in this issue --- "Event", "uselongdouble".
CC: ;
Subject: Re: [rt.cpan.org #96714] hangs forever on Event support test
Date: Thu, 2 Jul 2015 18:45:15 +0200
To: Slaven_Rezic via RT <bug-Coro [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
On Thu, Jul 02, 2015 at 01:27:55AM -0400, Slaven_Rezic via RT <bug-Coro@rt.cpan.org> wrote: Show quoted text
> > > According to Changes file this was fixed in 6.44.
> > > > Not according to the Changes file I published - where do you get this > > information from?
> > https://metacpan.org/source/MLEHMANN/Coro-6.46/Changes#L19 contains the terms mentioned in this issue --- "Event", "uselongdouble".
That it does, but I asked for the source of your information, I already know what I wrote in the Changes file. Or did you not read or understand it? It clearly doesn't say it is fixed (nor that it is a bug that could be fixed in Coro), and if you like to play pointless grepping games, it doesn't contain the terms from _your_ statement --- "fixed", "bug", so according to your methods, it clearly can't be the source of your statement. In any case, I am not sure what you were trying to say, but making up stuff yourself (as I suspect you did) isn't helpful for other people who might stumble over rt.cpan.org. You already abuse rt.cpan.org for your own purposes, which is bad enough for me, but when using it to spread information, you have a responsibility towards others, too. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schmorp@schmorp.de -=====/_/_//_/\_,_/ /_/\_\
On 2015-07-02 12:45:28, schmorp@schmorp.de wrote: Show quoted text
> On Thu, Jul 02, 2015 at 01:27:55AM -0400, Slaven_Rezic via RT <bug- > Coro@rt.cpan.org> wrote:
> > > > According to Changes file this was fixed in 6.44.
> > > > > > Not according to the Changes file I published - where do you get > > > this > > > information from?
> > > > https://metacpan.org/source/MLEHMANN/Coro-6.46/Changes#L19 contains > > the terms mentioned in this issue --- "Event", "uselongdouble".
> > That it does, but I asked for the source of your information, I > already > know what I wrote in the Changes file. Or did you not read or > understand > it? It clearly doesn't say it is fixed (nor that it is a bug that > could > be fixed in Coro), and if you like to play pointless grepping games, > it doesn't contain the terms from _your_ statement --- "fixed", "bug", > so according to your methods, it clearly can't be the source of your > statement. > > In any case, I am not sure what you were trying to say, but making up > stuff yourself (as I suspect you did) isn't helpful for other people > who > might stumble over rt.cpan.org. You already abuse rt.cpan.org for your > own purposes, which is bad enough for me, but when using it to spread > information, you have a responsibility towards others, too.
Nobody's talking about bugs in Coro. Where did you get that?