Skip Menu |

This queue is for tickets about the Sys-AlarmCall CPAN distribution.

Report information
The Basics
Id: 67239
Status: open
Priority: 0/
Queue: Sys-AlarmCall

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.2
Fixed in: (no value)



Subject: Tests fail with perl 5.13.x
See http://matrix.cpantesters.org/?dist=Sys-AlarmCall&maxver= for a test report overview. It seems that something broke with perl 5.13.x. Regards, Slaven
On Mon Apr 04 18:44:40 2011, SREZIC wrote: Show quoted text
> See http://matrix.cpantesters.org/?dist=Sys-AlarmCall&maxver= for a test > report overview. It seems that something broke with perl 5.13.x.
Thanks Slaven. Honestly I haven't looked at this code for ~8 years and don't really have any motivation to do so now. Back then I was just updating it for a consulting client to make it work with whatever was the shiny new Perl / mod_perl / whatever it was at the time. I'd be happy to pass on maintainer bits to someone else. :-)
FWIW, git bisect points at: 8165faea6ee20f11c287f0f531d49cc63ea9e6f3 is the first bad commit commit 8165faea6ee20f11c287f0f531d49cc63ea9e6f3 Author: Nicholas Clark <nick@ccl4.org> Date: Sun Apr 18 13:24:20 2010 +0100 Move PERL_ASYNC_CHECK() from POPBLOCK() to the kill case of Perl_apply(). This ensures that (safe) signals sent to the same process are still dispatched within the same statement (as before), without overloading the semantics of block popping.
On Fri Apr 15 23:42:38 2011, ANDK wrote: Show quoted text
> FWIW, git bisect points at: > > 8165faea6ee20f11c287f0f531d49cc63ea9e6f3 is the first bad commit > commit 8165faea6ee20f11c287f0f531d49cc63ea9e6f3 > Author: Nicholas Clark <nick@ccl4.org> > Date: Sun Apr 18 13:24:20 2010 +0100
It's a fair cop. However, Dave has just given me a "get out of jail free" card by fixing it blead: http://perl5.git.perl.org/perl.git/commit/011c381477c2b48fc4fbb6c52c59dbd6a21bc7d6 So everything passes once again. Nicholas Clark